You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AG won't finish loading and will simply close itself.
Here is what's going on:
22:44:14.819 [main] DEBUG c.a.a.receivers.PackageReceiver - Package receiver received intent Intent { act=android.intent.action.PACKAGE_REPLACED dat=package:com.adguard.android flg=0x4000010 cmp=com.adguard.android/.receivers.PackageReceiver (has extras) }
22:44:14.819 [main] INFO c.a.a.receivers.PackageReceiver - Package receiver received android.intent.action.PACKAGE_REPLACED for com.adguard.android
22:44:14.820 [main] DEBUG c.a.a.receivers.PackageReceiver - Handling our application update
22:44:14.824 [main] INFO c.a.android.receivers.BaseReceiver - Autostart is disabled and service is not running, we should exit[/
I guess Adguard should not react that way on its own update. Maybe we should simply ignore it.
The text was updated successfully, but these errors were encountered:
This actually might be correct, per the user. Folks who have an app set to not autostart wouldn't probably want it running just because of an update. I've several apps like this (not AG! 😉) at which I'd be irritated if they remain running/active just because the dev decided to push an update. (I even have those blocked in the AG firewall to give me some notice if they run unexpectedly.)
Steps to reproduce:
Here is what's going on:
I guess Adguard should not react that way on its own update. Maybe we should simply ignore it.
The text was updated successfully, but these errors were encountered: