MOBILE-273 : Using container for saving apk#95
Merged
manjunathnijaguna-fp merged 1 commit intomainfrom Feb 13, 2026
Merged
Conversation
manjunathnijaguna-fp
requested review from
alexzfp and
rajabhargava21
as code owners
rajabhargava21
approved these changes
Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Using container for saving APK.
Change summary
Even though the APK is present in the specified folder, the filename is dynamic, and the GitHub Action wasn’t able to reliably pick it up during the Firebase upload step.
To handle this properly, we’re resolving the APK inside the container and then pushing it to Firebase from there. This ensures the correct file is always picked up during publishing.