-
Notifications
You must be signed in to change notification settings - Fork 602
rename app distribution APK on upload #5044
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Yes, would love this feature for build variants/flavors. We use Github Actions and it would be great if we could pass build number like ${{ github.run_number }} and have it be part of the file name (if possible). |
Hi, is there any update on this please? |
This is really needed feature. any update on this? |
Hi folks, thanks for pinging this to our attention. Let me try bringing this up to our engineers to get some feedback. Update: Currently, we can't promise any timeline for this feature, however we've added this in our radar and we'll take it into account when prioritizing our upcoming work. |
Hi there, do we have any news about this please? |
Any updates on this? Thanks! |
Hi there, any updates here please? |
Any update on this? It feels like a big oversight. |
Just found out about this issue as freshly moved from appCenter to firebase distribution. File should stay at least exactly same as it was uploaded. Sure, some extra control with parameters will be great, but at least stop renaming it |
This thing is very annoying and taking away us from using app distribution. update on this will be highly appreciated. |
Just now, a tester from one of our clients complained that when they installed our app, it replaced one of their other apps. It turned out they had another "app.apk" file for another app in their download folder and installed that instead of our app. So, I would really appreciate this feature to be able to rename the APK. |
Please Google! This seems easy to solve and high-impact. It's almost always the case when testing new apps that you have a bunch of versions that you download, and having them called app(1).apk, app(2).apk, .... etc is really unhelpful when you're trying to try out different versions. |
One more Vote to please google for this |
Migrating from App Center to Firebase and just now realizing this bottleneck. This is definitely something to consider before making the switch, disrupts workflows. |
I'm in the same boat as alot of people here, in the progress of migrating from appcenter, to firebase. Simply having a generic app.apk, across a setup with 10+ apps will make our testing workflow quite a bit harder. |
Please, make this happen |
Please fix this issue. Thank you. |
This is really requires as it creates confusions to developers as to what version to download. |
Yes, please do something about it. Thanks |
Another soul migrating from AppCentrer to Firebase App Distribution. This feature would be very helpful indeed. 🙏 Thanks in advance! |
What feature would you like to see?
The app distribution gradle plugin should let testers download APKs with the same file name as when they were uploaded
Testers can currently only download files named "app.apk" no matter the name of the apk file that was originally uploaded
Using the "artifactPath" parameter in gradle is a problem when the Android application has more than one build variant.
Could we add a "artifactName"?
How would you use it?
This would let us keep meaningful names of APKs when distributing them from developers to testers. It would allow us to avoid mistakes when testing our mobile application
Both Jenkins and Gitlab let us control the name of the artifacts. We would like Firebase App Distribution to be our source of truth instead.
The text was updated successfully, but these errors were encountered: