Search Issue Tracker
Won't Fix
Votes
7
Found in [Package]
2.4.0
Issue ID
MNB-83
Regression
No
[Android] The first notification is sent 30-90 seconds late with Exact time Scheduling enabled when sending Repeating notifications
Reproduction steps:
1. Open the attached “IN-91475” project
2. Build the Android Player
3. Install it on the Android device
4. Make sure Notification permissions are enabled on the device for the specific App
5. Run the Android Player
6. Start a stopwatch to track the time taken for the notification to fire
7. Wait for the notification
Expected result: The first notification comes 30 seconds after the Player is started
Actual result: The first notification comes in over 1 minute after the Player is started
Reproducible with: 2.4.0 (2021.3.47f1, 2022.3.56f1, 6000.0.33f1, 6000.1.0b1)
Reproducible environments: Windows 11 (24H2)
Not reproducible environments: No other environments tested
Reproducible with these devices:
VLNQA00467 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 13
VLNQA00591 - samsung Galaxy S23 (SM-S911B), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 14
Note: If the notification is not a Repeating Notification, it is sent at the exact time
Comments (2)
-
cat_woods
Jan 10, 2025 13:36
we faced the same problem
-
German-Krasnikov
Jan 10, 2025 13:35
+
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
As per Android documentation, since API 19 repeating alarms are always inexact:
https://developer.android.com/reference/android/app/AlarmManager#setRepeating(int,%20long,%20long,%20android.app.PendingIntent)
While it is possible to make them exact by repeatedly scheduling one time alarms, there is a general direction from Google to not use exact alarms at all, henci fixing this bug would be move in an opposite direction from us. If users really needs this, our Java code is available for them, they can use modified version of this package.