jamie-mh
Add Pixel 9 (pro) support
Currently i cant install the app on my new Pixel 9 pro. Neither from Google Play Store (used the link here) or F-Droid repo. Would be nice to be able to use it on my new phone as well. Not sure if its a bug or by intention. Therefore i filed a feature request instead of a bug.
Thx.
exactly f-droid show "no versions compatible with device". There is a option to show all version and install them. But didnt tested this yet. Google Play Store show something equal.
I'm not sure it's related to the Pixel 9 Pro XL. I tried to install Authenticator Pro for the first time today on my Pixel 7 Pro using F-Droid, and F-Droid claims that there is no compatible version.
From About phone settings, Android version is 14 and build number is AP2A.240805.005.
Allowing Incompatible version warnings and installing anyway gives:
INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113
Relevant Stack Overflow link:
https://stackoverflow.com/questions/24572052/install-failed-no-matching-abis-when-install-apk
Is it possible that Android 14 dropped support for an older ABI (application binary interface) that this app is compiled with?
Not available on Pixel 9 Pro either. Not in play store not compatible on Izzy or other f-droid clients either.
No problem with my Pixel 9 XL pro Working fine. Took the .apk here
Android 14 Build AD1A.240905.004
The arm64-v8a version of the release from this github repository works for me on the Pixel 9 Pro XL
The arm64-v8a version of the release from this github repository work for me on the Pixel 9 Pro XL
That indeed installs, thanks.
Perhaps the issue is that the play store and fdroid is missing whatever data is needed to show compatibility.
I can confirm on my Moto G84, android 14, google play system update on August 2024. I tried installing from the Izzy's repo, version 1.25.2 and found this. I use Droid-ify f-droid client and tested installing via both shizuku installer method (silent install) and session installer (prompts for manual install like apk sideloading). The app installs fine via both methods.
But upon launching the app, android complains that the app isn't compatible with the latest version of android (attached screenshot). Fortunately, it goes away after tapping OK and subsequent launches don't trigger the warning.
My other device, Samsung M51 is on android 12 so I guess that's why it never complained when initially upgrading to this version back in June.
Edit: I've no idea why this screenshot looks so gigantic, sorry :-P Edit2: Might be a duplicate of #1083 ?
This is what I get when I follow the Google play link in the readme on a pixel 9 pro.
This is what I get when I follow the Google play link in the readme on a pixel 9 pro.
See #1162.
Pixel 7 and later drop 32-bit apps support. 32-bit apps can't be installed and executed on Pixel 7 and later devices no matter what. This is tied to specific device models, not Android version.
The package of Authenticator Pro distributed on IzzyOnDroid targets only armeabi-v7a (32bit arm devices).
This means Authenticator Pro from IzzyOnDroid only runs on devices that support 32-bit apps. Newer Pixels don't support 32-bit apps, so F-Droid clients mark them as incompatible and won't install them.
The package on IzzyOnDroid needs to be updated to include arm64-v8a (64-bit arm) using fat APK or by including multiple variants, if possible.
If you're experiencing this problem, get the app from Google Play beta mentioned in #1162, or get the package labeled as arm64-v8a from GitHub releases.
Pixel 8a has the same problem. Izzy and the 1st party repo both show incompatible, but the direct download from GitHub works a charm.
Yes, it seems like it's missing the arm64 versions in Izzy's repo.
Why is that, @izzysoft? The size of the apks?
Yupp. There's a per-app size limit of 30 MB (so strictly speaking, even a single APK is already beyond that) – and we can only take 1 APK per release. If @jamie-mh wants we can switch to the arm64 one, which then would drop support for all 32bit devices though.
