Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.0.2
Issue ID
1140272
Regression
No
[Mobile Notifications][Android] Repeating notifications with significant time spans aren't delivered on specific devices
Repro steps:
1. Open QA attached project "repro_1140272"
2. Build and run on Android
3. Open the app
4. Close the app and go to device's settings
5. Turn the time of the device one-day forward
6. Wait for the notification
Actual: The repeated notification isn't delivered
Reproducible with Mobile Notifications package version 1.0.2
Tested and reproduced on this device:
VLNQA00278, Xiaomi - (Redmi Note 7), Android 9, CPU: Snapdragon 660, GPU: Adreno (TM) 512
Didn't reproduce on these devices:
VLNQA00176, Xiaomi Redmi 4 (Redmi 4), Android 6.0.1, CPU: Snapdragon 430 MSM8937, GPU: Adreno (TM) 505
VLNQA00218, Samsung Galaxy Note9 (SM-N960U), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00166, Huawei P20 (EML-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
VLNQA00052, Xiaomi MI MAX (MI MAX), Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note:
Seems that this is only reproducible on a Xiaomi device:
Seems that Huawei (including Honor) and Xiaomi utilize aggresive batter saver techniques which restrict app background activities unless the app has been whitelisted by the user in device settings. This means that any scheduled notifications will not be delivered if the app is closed or not running in the bacgkround. We are not aware of any way to workaround this behaviour besides encouraging the user to whitelist your app.