Hi everyone,
During my recent production release, I encountered something unexpected and would appreciate some clarity. I created separate builds for two different MDM teams, each with a distinct package name. However, I noticed that the download link generated for both builds was the same, even after a third attempt to generate the build.
Is this expected behaviour?
From a technical standpoint, since the only difference between the builds is the package name, I would assume that each build would have its own unique link. In this case, it seems like different builds (with different package names) are being associated with the same download link, which has caused confusion on the client side.
Has anyone else experienced this, or could this indicate a potential issue with the build or link generation process?
Also, please let me know how I should share two different package builds with the client for two different MDM teams.
2 Likes
Package name is internal to any application.
Typically you rename the app name before the build is processed and then rename the APK post download before sharing it to client.
2 Likes
Thank you for raising this question.
Changing the package name allows two instances of the same application to run simultaneously on a single device. However, in your specific use case—where you need to share a link from Designer with the client—it’s more relevant to update the applicationName and version, as these are part of the URL structure used by the Designer.
The packageName, on the other hand, is not part of the URL and therefore does not influence how the application is accessed through the link. This means that changing the package name won’t help in your scenario.
Currently, the issue you’re facing—where the new build replaces the old one—is happening because all identifiers (application name, version, etc.) are the same. Updating the relevant settings should resolve this.
Sample Url -
https://vahana-designer.s3.ap-south-1.amazonaws.com/flutter/49720169685714180365536/48388169804659612998044/UAT/1.5.9/AUACE_v1.5.9.apk
3 Likes
Thank you for the detailed explanation.
I understand that changing the applicationName and version is key for generating a unique URL in Designer, and that the packageName doesn’t impact the URL structure.
However, I have a concern regarding changing the applicationName. If we modify it just to generate a different URL, won’t the installed app on the user’s device also reflect this new name? This could lead to confusion for end users and potentially raise issues with the client’s marketing or branding team, as the application name is a visible and important identifier for them.
We have two different teams that need to distribute the same application to their users, with the same app name and version name.
Would changing only the version code for each team’s build prevent one build from replacing the other?
Any best practices or alternative approaches would be appreciated.
1 Like