Skip to content
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

[Bug]: Unresponsive Notifications on Xiaomi Devices #2070

Closed
1 task done
bundleberk opened this issue May 1, 2024 · 1 comment
Closed
1 task done

[Bug]: Unresponsive Notifications on Xiaomi Devices #2070

bundleberk opened this issue May 1, 2024 · 1 comment

Comments

@bundleberk
Copy link

bundleberk commented May 1, 2024

What happened?

After updating the SDK to 5.1.8, on most of the Xiaomi devices when user clicks a notification, nothing happens.

I believe the issue is the "Display pop-up windows while running in the background" permission in the "other permissions" section on Xiaomi devices is "not granted" by default after installing the app with the 5.1.8 SDK.

After I grant the permission, notifications work properly. Also it works properly on OneSignal 4.8.7 even if this permission is not granted on Xiaomi devices. Something seems to be changed about this on OneSignal 5.x.x versions.

Steps to reproduce?

1. Find a Xiaomi device.
2. Install an app that has OneSignal 5.1.8 SDK.
3. Check if the  "display popup windows while running in the background" is granted or not.
4. Send a push notification.
5. Click notification.

try it again after granting the permission from "other permissions".

What did you expect to happen?

I expect the notifications open the app when clicked, in this case notifications disappear when clicked but nothing happens after.

OneSignal Android SDK version

Release 5.1.8

Android version

13, 12, 11, 10, 9

Specific Android models

most of the Xiaomi devices.

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jkasten2
Copy link
Member

jkasten2 commented May 3, 2024

@bundleberk Thanks for reporting, however there is another open issue #2042 that covers this. I am merging this one into existing one so we have one thread to track this issue. Please follow issue #2042 for updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants