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.
Updated: https://www.notebookcheck.net/Google-Pixel-8-Pixel-8-Pro-benchmark-block-lifted.759613.0.html
Google has lifted the block it placed on the ability for users to freely install benchmarking apps on its Pixel 8 and Pixel 8 Pro smartphones. The block had been in place during the review embargo period but extended past the on sale period where customers purchasing the devices couldn’t install benchmarks on their new Pixels either.
That is insane. Straight up blacklisting popular software because they don’t want people to look too closely at what they purchased. It’s amazing what the public is willing to accept, just such a constant stream of reports about bad behavior from companies that most people can’t find the energy to care.
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.
Android 14 uses new APIs and Google requires everyone to update their SDK to say whether or not it uses the new APIs. If they did nothing it was flagged as an incompatible app, but if they don’t use the APIs it will run fine.
You can usually adjust your app and publish an update without needing to change the app’s targetSdkVersion. Similarly, you should not need to use new APIs or change the app’s compileSdkVersion, although this can depend on the way your app is built and the platform functionality it’s using.
https://developer.android.com/about/versions/14/migration
You can update the SDK without triggering an update to the app and it will be available on the play store.
Occam’s razor applies here.
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.
