Can't tell if on purpose or broken by mistaken (no documentation updates, so maybe broken?)
ACTION_PACKAGE_ADDED cannot be received unless app is a Process.SYSTEM_UID developer.android.com/reference/andr
cs.android.com/android/platfo
commit : cs.android.com/android/_/andr
Conversation
Probably meant to be a privacy related change? No more ad networks or apps snooping on package adds?
Though, no bueno that this isn't documented or shared anywhere I can find :\
1
Replying to
The QUERY_ALL_PACKAGES permission provides access to most (all?) of the past functionality. Not sure about this case though.
developer.android.com/about/versions
If you don't have that permission, you can only see apps that you've marked as being available to the app.
1
For apps targeting API 30+, they're only supposed to be able to see apps in their whitelist unless they request QUERY_ALL_PACKAGES. A lot of changes were made to support this. For now, anyone can use QUERY_ALL_PACKAGES and it's not user-facing yet. It will likely get locked down.
1
It just doesn't make much sense for them to start heavily locking it down when apps can simply drag their heels and avoid adopting API 30+ until it becomes mandatory on the Play Store at the end of next year. This way, at least app manifests will have a list of apps or that perm.
Replying to
Makes sense. I was assuming there will be a big wave of breakages when they start forcing people to provide bundles vs apks, leading to all these have a hard depricated date as well
1
Replying to
It's not clear if they're really going to do that any time soon. They've toned down the warnings for releases without app bundles. They could require people to generate a bundle of apks with bundletool and get the same benefits for anything but an app with updates anymore.
1
Show replies