Installer App settings is not working properly.
Please check before submitting an issue
- [X] I know what my device, OS and App Manager versions are
- [X] I know how to take logs
- [X] I know how to reproduce the issue which may not be specific to my device
Describe the bug
I'm using the latest am debug from telegram. My issue is whenever I try to install any apk file from AM debug app , I'll have to manually change installer app everytime. Even If I set Play Store as a default app in AM debug installer settings.
To Reproduce
- Set installer app to playstore or anything you want
- Now try to install apk using AM debug, it will show Am debug as installer instead of Play Store.
Expected behavior
It should use the same installer app which I selected I AM debug settings.
Screenshots
Logs
No response
Device info
- Device: Redmi Note 7 Pro
- OS Version: Android 14
- App Manager Version: version 4.0.0-beta01-DEBUG
- Mode: Root/ADB/NonRoot: Root - Magisk 270006
Additional context
It was working fine in some old stable releases , but I forgot the exact version code.
I cannot reproduce it. Please make sure App Manager is running as root/ADB or any other privileged mode, otherwise it will display AM Debug due to a lack of permission.
I cannot reproduce it. Please make sure App Manager is running as root/ADB or any other privileged mode, otherwise it will display AM Debug due to a lack of permission.
But I've already given root permission to it tho , As I said it only show the selected installer app for sometime then it changes back to am debug , It never picks the default installer app from the am debug settings. I've to manually select it most of the time while installing any apk.
Sorry, still cannot reproduce it.
Sorry, still cannot reproduce it.
Strange, It is still the same for me whether I use ksu or magisk.
The default installer app settings doesn't persist & reset automatically back to App manager after a couple of minutes.
If this happens, I would just turn it to Wireless Debugging. It might fix it. Remember root is usually buggy.
Sorry, still cannot reproduce it.
Okay,heres what i think is happening. Did he use custom option or the normal one? because this is happening to me too in adb. Also happening in normal app manager