-
If you are looking for help, please confirm the following...
Which mobile framework are you using?Flutter (Dart) Steps to reproduce
publishing:
firebase:
# authenticate via service account
firebase_service_account: $FIREBASE_SERVICE_ACCOUNT
android:
app_id: {my_app_id}
groups:
- Alpha
artifact_type: "apk" Expected resultsI've added a script that runs after the Shorebird build command to verify that the apk Command echo "🔍 Checking APK directory contents..."
ls build/app/outputs/apk/release/ Output
Since the APK (app-release.apk) is clearly present in the release folder, the subsequent publishing step should find this APK and push it to Firebase App Distribution as a new release. Publishing Config publishing:
firebase:
# authenticate via service account
firebase_service_account: $FIREBASE_SERVICE_ACCOUNT
android:
app_id: {my_app_id}
groups:
- Alpha
artifact_type: "apk" Actual results
Publishing Output
Build id (optional)6537d06ddaa4bfe81980fe16 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
hey @movaid7, i think you are missing a section in your yaml file where you specify what files or outputs should be saved
like this you define the artifacts that should be collected and saved after the build process is completed |
Beta Was this translation helpful? Give feedback.
hey @movaid7, i think you are missing a section in your yaml file where you specify what files or outputs should be saved
like this you define the artifacts that should be collected and saved after the build process is completed