-
Notifications
You must be signed in to change notification settings - Fork 286
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
Repeated notification when location disabled due to redundant checks #656
Comments
I will check this issue. We need detail clarification on this issue. |
@eyganeshv , post questions you have about this issue here and we will do our best to address them. |
This issue is seen for Android also. |
@NaziyaNazir, reproducible steps are same for android? |
@ArchanaNair Yes, the repro steps are same. |
May I know the OS version? I am unable to reproduce it on Android, verifying it on OS version 9 |
@ArchanaNair OS version is Android 9. |
@NaziyaNazir , I could see the issue when app goes to background and again comes to foreground, but not in the scenario which is given in reproducible step. |
This is starting to sound like a low priority issue, anybody disagree? |
@tremblerz @NaziyaNazir included a fix for this in android in PR #764 |
I could not get this to reproduce on iOS or Android anymore. I believe it was fixed in #749 |
Yes the issue is fixed in android also. |
Version
Steps to reproduce
Go to Settings, turn off location
Expected Behavior
Any event should generate notification only once in general, the way we trigger notification in our app is asynchronously checking states at every screen mount/refresh, we need to shift the logic perhaps
The text was updated successfully, but these errors were encountered: