Closed Bug 1477177 Opened 3 years ago Closed 6 months ago
Install is failing on the Samsung store with "Unable to install application due to error popup"
We are experimenting to get Fennec on the Samsung store and the install is failing with: > Unable to install application due to error popup (Installation failed. Try later.org.mozilla.firefox: - 113) See the video as attachment
I tried to upload aarm64 and I am getting: "The VersionCode is invalid. VersionCode must be entered in integers and the same version number cannot be used for more than one binary." I downloaded it here: https://ftp.mozilla.org/pub/mobile/releases/61.0/
Assignee: mozilla → nobody
Component: Android partner distribution → General
I also asked a question to their support.
I moved the package as beta and I can reproduce (samsung devices only): http://apps.samsung.com/betastore/openAppDetail.as?appId=org.mozilla.firefox AFAIK, I didn't have this issue with 60.
(In reply to Sylvestre Ledru [:sylvestre] from comment #1) > I tried to upload aarm64 and I am getting: > "The VersionCode is invalid. VersionCode must be entered in integers and the > same version number cannot be used for more than one binary." This is very specific; it means that we have overlap with ARM, x86, and aarch64. I remember thinking this was a potential problem but being calmed by jchen's analysis in https://bugzilla.mozilla.org/show_bug.cgi?id=1360291#c3. jchen, what do you think is happening here?
:jlorenzo in bug 1477259 said it's because aarch64 has the same version code as x86. For the error in comment 0, :sebastian said it's due to ABI mismatch. I do see this in the logs locally, > E PackageInstaller: Commit of session 2095308263 failed: Failed to extract native libraries, res=-113 > D AppsPackageInstaller: PackageInstallerCallback: result , message [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113], packageName [org.mozilla.firefox] > D AppsPackageInstaller: INSTALL failed. > D [GalaxyApps Install] : [ERROR] Package install return code : -113
Jim, is it because aarch64 wasn't uploaded? If not, do you see what could be the reason of the issue? Thanks
Wrong Chen, sorry.
(In reply to Sylvestre Ledru [:sylvestre] from comment #6) > Jim, is it because aarch64 wasn't uploaded? > If not, do you see what could be the reason of the issue? > Thanks aarch64 shouldn't be related. :sebastian said it could be because Samsung store always serves the highest version code APK, which in our case is the x86 version. Is there a filter or something in the Samsung console that lets you restrict a particular APK to a particular ABI?
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.
Priority: -- → P5
I uploaded only fennec-60_0_2-multi-android-arm.apk (no x86, no aarch64) and published it on: http://apps.samsung.com/betastore/openAppDetail.as?appId=org.mozilla.firefox I am getting the same error -113. Jim, can you help?
Priority: P5 → P2
So, uploading only the arm worked. I had to uninstall and reinstall the application. While I don't think x86 is a priority, fixing the issue for aarch64 should be done soon.
Maybe we can find a contact at Samsung? I suspect the Samsung store may not be handling multiple APKs with different ABIs correctly. It would be good to get a confirmation.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.