Android 14 incompatible warning

[truthsword]

Describe the bug When I installed this to my Pixel 5a, I got a warning that the app is incompatible with my Android version. Still it installed.

To Reproduce Steps to reproduce the behavior: Install on device with Android 14

Expected behavior No compatibility warning

App Version 1.24.0 F-Droid sourced

Additional context Add any other context about the problem here.

[Kenny417]

I'm also seeing this on my Pixel 6 Pro running Android 14 (January 5, 2024 update). This is my first time using the app so I don't know if this a new bug or intentional.

Android 14 has been available since October.

[jamie-mh]

Hi,

Can you please provide the exact wording of the warning message? The app targets Android 14 (SDK 34) so there shouldn't be a warning. Indeed, I can't reproduce the issue on an Android 14 emulator nor my physical device (S22 with Android 14).

Thanks

[Kenny417]

This app isn't compatible with the latest version of Android. Check for an update or contact the app's developer.

This happens on first launch after installing it. I was able to reproduce it for this screenshot but clearing cache and app storage. After I tap OK, it seems like I can use the app normally.

[truthsword]

My installation was from Izzy. Would that make a difference?

If I ran a backup and then uninstalled, deleting cache/memory storage, would the backup restore include my settings?

EDIT1: OK... I see the screenshot has already been posted. That's the one I recall as well. I believe this may be related to the latest Google API.

[Kenny417]

It seems like maybe this is an error that happens when running a 32 bit app on a 64 bit device, if that helps you test this @jamie-mh

https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/core/res/res/values/strings.xml;l=5420?q=deprecated_abi_message%20f:strings.xml%20%22compatible%20with%20the%20latest%20version%20of%20Android%22%20%20

[truthsword]

I'm unsure this case is bitness related, as I have many apps on my phone, and I doubt that they are all 64-bit. Yet this is the only installation where I've seen this warning.

[Kenny417]

@jamie-mh Is the armeabi-v7a version the one uploaded to the Izzy / Fdroid repo? When I scroll down to the bottom of this page, that's the version it shows. That's not the right version for my Pixel 6.

I just manually installed the me.jmh.authenticatorpro-arm64-v8a.fdroid.apk version from the Releases page in this repo and did not get the incompatible message on first launch.

It's late and I'm exhausted so I may be completely wrong here, but I feel like the wrong version was uploaded to Fdroid or I somehow downloaded the wrong version from Fdroid.

[truthsword]

That's interesting as the download I received from Izzy is named me.jmh.authenticatorpro_100000092.apk

EDIT: I uninstalled and went to Google. This is the first time FDroid has failed me (and the first time I've used Izzy). Install happened without popup warning.

Notably the Google Play Store did not recognize that the Izzy version app was installed, so apparently something is amiss with the version from Izzy.

[jamie-mh]

Yes, the version on Izzy's repo is the 32-bit version (see #724 for info). Since the error message is unique, that seems like the most likely explanation.

@IzzySoft would switching to the 64-bit build be seamless for users (provided they have a 64-bit device of course) ?

Cheers

[Kenny417]

Ah, I see. That issue #724 clears it all up for me. I'll probably experiment with using Obtanium to download the version I need from this repo so I can keep getting updates when they are released as opposed to side loading each update manually.

I'll keep following this Issue though since using the Izzy repo on Fdroid is more ideal for me in the long run.

[IzzySoft]

would switching to the 64-bit build be seamless for users (provided they have a 64-bit device of course) ?

If the versionCode of the 64bit one is always equal or higher than the one of the 32bit, yes. But those on "pure 32bit" devices are then stuck and won't receive updates anymore.

When I one day have the spoons for it (too many other tasks at the moment), I might set up another repo for "legacy devices"…