-
Notifications
You must be signed in to change notification settings - Fork 129
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
app crushed after changing notification status and coming back to app #168
Comments
Same issue, when notifications are turned off, app crashes in the background. Android 13 |
Same here..this also happens with the package 'permission_handler'. |
As far as I understand, this issue is similar to #163 |
Same here |
Same, |
As far as I know, this issue is not related to the plugin. It is the intended behavior of Android OS to restart the app when permissions change from "allowed" to "denied." Now, when you run the app with the debugger, Android restarts the app, but the debugger loses its connection and displays a white screen. If you try this in Release Mode (without the debugger), the app simply starts over from the beginning, with the permissions denied. I believe there is no way to avoid restarting the app. If you want to create the illusion that the app has not restarted at all, you must manually save and restore the app state on your own, similar to what WhatsApp and Spotify do. |
I have the same issue .. I tried app_settings 5.1.1 and app_settings 4.1.8 on Android 34 and I got the same result! |
AppSettings.openNotificationSettings()
After changing notification status and coming back to app, my app crushed.
It does not happen with Galaxy Note 10+(Android12), Galaxy Z flip3(Android12), but it does with new Galaxy phons such as Galaxy S21(Android13), S22(Android13).
The text was updated successfully, but these errors were encountered: