-
Notifications
You must be signed in to change notification settings - Fork 9
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
Prompt for cache refresh #8
Comments
Output describing the situation above
|
No further testing possible on this phone. Accidentally erased my data doing a second complete uninstall without the -k flag. Whoops. Big sad |
Happened to me. Same error, same resolution: a phone reboot. |
Should we ask the users to restart their phone regardless, or only if they experience the issue? |
I would prob aim for only if they experience the issue. Though, that would require that the script can read values generated from ADB from the terminal. I'm not sure if that is possible from the BAT Script. It prob is possible from the *Nix and Powershell tho Your call broski |
I have 1 day (well literally 8 minutes now) before the app has to be updated from 2.23.23.78 to whatever is here now that made Issue #6 . As Im a big procrastinator lol. I tried to see how this utility works on my old phone with Android 8.0 ahead of dealing with possible Issue #6 issues
I interestingly enough had a more easy time than I did on my Android 10 device where I didnt run into Issue #4 . So the problem for #4 which I submitted a PR doesnt happen until after a certain Android version (probably 9.0)
But I did run into an new issue.... "[INSTALL_FAILED_VERSION_DOWNGRADE] " as described in Issue #2 .
In my case app was uninstalled successfully uninstalled . The older OS didnt update/refresh the nstalled software package cache/manifests somewhere on the phone which somehow causes that error to show up. Restarting the device and manually installed removed it. Perhaps might need a modification to read the errorcode/success value and prompt for that as restarting or if possible manually refreshing the cache should be considered.
Everything else went as expected
The text was updated successfully, but these errors were encountered: