Fixed
Status Update
No update yet.
Comments
vi...@google.com
vi...@google.com
ad...@google.com
ad...@google.com
We have passed this to the development team and will update this issue with more information as it becomes available.
ad...@google.com
The requested feature will be available in a future build.
lb...@gmail.com
@3 That's great news!
Can you please explain how it will work, and if by "future build" you mean Android S (Android 12) ?
Can you please explain how it will work, and if by "future build" you mean Android S (Android 12) ?
Description
Someone else from Google told me it's not package name that's needed, but label instead (which is also incorrect) :
And another said that it is required:
And the docs themselves don't mention about it being required at all for the package name to be set for INSTALL_REASON_USER to work properly, either:
In fact it says it's optional, and that during install if the package name doesn't match what's provided or if the multiple APK files don't match each other, it will fail.
This means the installation itself already does fetch the package name.
Please make setting the package name deprecated or completely optional for INSTALL_REASON_USER to work properly and create an app icon on the launcher.
It doesn't make sense that it's needed before the installation has begun, if the installation itself already gets it.
This can help in case we want to install an APK from adb, but we don't know the package name.
The adb command doesn't let us provide the package name automatically. It needs us to check what is the package name ourselves.
Please make adb also be able to handle it without a package name.