cross-posted from: https://lemdro.id/post/2289548 (!googlepixel@lemdro.id)
According to the comments section, users have been able to sideload them without issues. Play Store has since begun allowing the installs.
cross-posted from: https://lemdro.id/post/2289548 (!googlepixel@lemdro.id)
According to the comments section, users have been able to sideload them without issues. Play Store has since begun allowing the installs.
It was an android 14 compatibility issue and the app has since been updated and runs fine.
The app hasn’t been updated but the Play Store block has indeed been lifted. People were sideloading without issue. Perhaps Google intended for the block to only last until launch to prevent reviewers only.
There is actual compatibility, and official compatibility.
The updated apps likely didn’t have any code changed. (why they still worked when side loaded) Instead, the Play Store listing updated the compatibility filter to include Android 14, so 14 users could now see them in the Play Store.
It’s not an uncommon practice. Many apps might simply have a compatibility filter like “yes if [OS version > X]”. But that can be a problem if some future OS breaks compatibility. Especially in the case of a benchmark app that’s supposed to give comparable results between OS versions. If the new OS tweaks something that doesn’t fully break the benchmark, but causes inaccurate numbers, that would need to be checked before it gets approved.
I’m not seeing updated versions of the listings on my end (in terms of the last updated entry). Unless compatibility can be set separately?
Ah, so I fell for reactionary bs assuming that a fairly well written article had good information? Dammit. =P Thanks for the info, that sounds a lot more plausible to me.