-
-
Notifications
You must be signed in to change notification settings - Fork 747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: no way to identify why app installation failed #1030
Comments
I am currently working on the fix. Can you please turn off the Google Play Protect for some times and try to install the app again and share me the results please? |
The same happens to me when I install revanced |
I'm uncomfortable because I don't know if the installation is in progress |
I think the callback should be removed if it's not possible to pop the dialog ONLY when it errors The dialog needs to stay for two reasons:
|
On a related note, the package installer dialog also does not appear when updating the Manager from within the Manager. Movie001.mp4 |
Type
Error at runtime
Bug description
There will be cases where one may be forced to uninstall the manager due to some issue and the user could have forgotten to backup the keystore. In such cases when updating a patched app over an existing patched app will end app with the message "app not installed as package conflicts with an existing package". But after the recent update and l presume with the fix #1021, when clicking install the pop up after installation just disappears. If installed successfully, the manager will say installed. But if it fails there is no way to know what's the issue and manager just says installing.
Steps to reproduce
Android version
Android 13
Manager version
1.4.1
Target package name
Any
Target package version.
Any
Installation type
Non-root
Patches selected.
Nil
Device logs (exported using Manager settings).
Installer logs (exported using Installer menu option) [unneeded if the issue is not during patching].
No response
Screenshots or video
screen-20230716-010252.2.mp4
Solution
No response
Additional context
No response
Acknowledgments
The text was updated successfully, but these errors were encountered: