Hello, I’m being shown the following message:
This app was built for an older version of Android and cannot be updated automatically
I don’t mind that the app won’t be updated automatically. But the installation still fails?
Which app is it? Can you give a link as well pls.
1 Like
Sorry, forgot. It’s this one: Barcode Scanner | F-Droid - Free and Open Source Android App Repository
Also, additionally, I have noticed that only the big “Install” button up top is enabled. The little buttons for each individual version, are still disabled. UI bug?
1 Like
Works for me. Probably your device is either not compatible, or the android version you have does not allow that.
For individual versions one, not sure why it does not show that.
Meanwhile, try one of these: QR & Barcode Scanner | F-Droid - Free and Open Source Android App Repository
Or
[lWS.QR] lightweight Web Server QR code | F-Droid - Free and Open Source Android App Repository
1 Like
Thanks for your reply.
Sorry, but I don’t understand. What could be the reason for this?
So you’re saying “This app was built for an older version of Android and cannot be updated automatically” is true - and it shows this message for you, too - but there’s another issue which has nothing to do with this message, which leads to the installation failing in the first place?
But is it like this for you, too? Sounds like a UI bug then, no?
Do not think it is a UI bug, maybe compatibility issue. Depends on the phone make or android version.
Also go to advanced/expert settings under F-Droid and check the unstable version as allow.
Also a bit up, under app compatibility, allow the incompatible version.
Now close the app, clear cache and reopen. Check what the barcode one shows now.
1 Like
Which device? Android version? Exact error message on install?
1 Like
No, sorry, I think you misunderstood: I was saying the disabled install buttons look like an UI bug to me. Because why would the big main install button be enabled, but the smaller ones below, for the individual versions, are still disabled.
Doesn’t change the outcome.
Samsung Galaxy A14 5G, Android 14
I press the big main install above, get asked to confirm “App incompatible with your device, install anyway? No Yes”, when confirming, there’s an Android pop-up asking “Barcode Scanner Do you want to install this app? Cancel Install”, then the final error message “Error installing Barcode Scanner Failed to install due to an unknown error”.
Ah, ok, it’s a know issue Prevent incompatible apps from being installed - targetsdk too old (#2847) · Issues · F-Droid / Client · GitLab already fixed, soon in an alpha version, today in nightlies
it offers more details when you expand Versions in app details
Android 14 can’t install apps that target Android 6 or older (it can be force to install it via adb but F-Droid Client can’t)
Binary Eye | F-Droid - Free and Open Source Android App Repository should work fine
1 Like
Hmm let me see if I got that: You’re saying F-Droid shouldn’t even offer to install at all because the app’s targetsdk is too low, which doesn’t allow APK installation without adb? I assume that also fixes the “UI bug” because the disabled install buttons below were correct to be disabled after all?
Yeah there’s lots of alternatives 
It was more about finding out what’s going on here, than the actual app itself.
yes, just a bug, such is software
Of course! Thank you very much for your help. 
It’s just that I wasn’t aware of this targetsdk restriction for manual APK installation. Doesn’t the Google Play Store already restrict listed apps to certain targetsdks? Isn’t that enough “security”? Feels overreaching to require adb, too, and to not even make it a setting like you have to enable manual APK installation in the first place…
these are not 2 separate things
that’s a dev workaround, so they can test APKs
Fair enough! Then let me rephrase: Why isn’t it enough for Google to apply their vision of security to apps listed on the Play Store, i.e. not listing them or allowing installation from the Play Store if targetsdk too low - why does this restriction have to be applied to Android itself without any chance to opt-out?
That’s what I meant when I say they’re overreaching.
As if it’s not bad enough already that root isn’t available by default. And if I do root my phone, some apps refuse to work, because a rooted phone obviously means I must be up to something. 
“security”
also it’s Android by Google
You can of course build your own Android from the open-source part and set it as you wish
Less and less reasons to need root today, why do you need it?
This is technically true of course. But if you look at the difference in effort required between that and a theoretical simple toggle switch “I understand the risk, allow old targetsdk” in the settings menu, it’s not a fair comparison. It’s David vs Goliath. There comes a responsibility with that kind of power that Google has. In my opinion, companies shouldn’t be allowed to get away with just anything, similar to the Right to repair discussions regarding Apple.
Very off-topic of course.
Ah, well… it’s various things. I switched to this new Android 14 phone just recently and I’m still in the process of setting everything up. For example, with my old rooted phone I was able to automatically and continuously backup my contacts database from /data/data/com.android.providers.contacts via SSH. Not sure yet, what my options are on a non-rooted phone. I’m sure there are solutions, but it still feels like making me jump through hoops.
None of the contacts app have a “daily backup” to storage? Open some feature-requests/issues then
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.