Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
1.0.0
Issue ID
1163354
Regression
No
Unity Mobile Notification package shows too many alarms when using Samsung devices
To reproduce:
1. Open attached project
2. Build and run to Galaxy device
3. 3 times go in the background of the app
4. Check logcat
Actual result: notification of SamsungAlarmManager: !@Too many alarms (500) registered from uid 10136
Expected result: should be only 200 alarms
Reproduced in: 2018.4.4f1; 2019.3.0a9
Tested with:
VLNQA00150, Samsung Galaxy S9 (SM-G960U), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00111, Samsung Galaxy J5(2016) (SM-J510FN), Android 7.1.1, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 306
VLNQA00093, Samsung Galaxy S6 edge (SM-G925F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
Note: Attached logcat
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
This is a duplicate of issue #1165178