Fix publish.yml so that the downloaded artifact can be found

BloomBooks · Sep 14, 2023 · fc1fc0f · fc1fc0f
1 parent 4f63ca6
commit fc1fc0f
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
@@ -43,10 +43,11 @@ on:
             releaseChannel:
                 type: string
                 required: true
+run-name: Publish ${{ inputs.platform }} - ${{ inputs.releaseChannel }} (${{ inputs.runId }})
 
 jobs:
     publish-mobile:
-        name: Publish Mobile App
+        name: Publish ${{ inputs.platform }} - ${{ inputs.releaseChannel }} ()
         runs-on: ubuntu-latest
 
         steps:
@@ -67,19 +68,22 @@ jobs:
               uses: dawidd6/action-download-artifact@v2
               with:
                   run_id: ${{ inputs.runId }}
-                  path: ./artifacts
+                  path: ./packages/mobile/artifacts
                   name: BloomReaderLite-${{ inputs.platform }}-${{ inputs.releaseChannel }}
                   search_artifacts: true
 
             - name: "Debug: List directory contents"
               run: ls -l artifacts
+              working-directory: packages/mobile
 
             - name: Find Build Artifact
               id: find-build-artifact
               # Note: We are expecting the artifacts folder to only contain one file in it, which is the APK or IPA file for the requested platform/releaseChannel
               run: |
                   artifact_path=$(find ./artifacts -name 'build-*')
                   echo "artifact=$artifact_path" >> $GITHUB_OUTPUT
+              # Note: It is more straightforward if this is run from the same directory that "eas submit" will be run from.
+              working-directory: packages/mobile
 
             - name: Setup EAS
               uses: expo/expo-github-action@v8