Search Issue Tracker
Fixed in 1.3.2
Votes
7
Found in [Package]
1.3.0
Issue ID
1254664
Regression
No
[Mobile Notifications] iOSNotificationLocationTrigger is not firing on iOS devices
How to reproduce:
1. Open the attached 'PushNotifications.zip' project
2. Build for iOS and open the Xcode project
3. Deploy Xcode project to an iOS device
4. Allow Push Notifications
5. Press 'SceduleGeo' button
Expected result: Pop-up window shows up as a result that iOSNotificationLocationTrigger is fired successfully
Actual result: Pop-up window does not show up as iOSNotificationLocationTrigger is not fired
Reproducible with: 2019.4.9f1, 2020.1.3f1, 2020.2.0b3(1.0.3, 1.3.0)
Could not test with: 2018.4.27f1 (due to errors)
Reproducible with:
iPhone 8+ (iOS 12.0)
iPhone XR (iOS 13.4.1)
iPad 9.7 6th gen (iOS 14.0b7)
Notes:
- Push Notifications are requested and allowed
- Core Location Service requested and running with the "When in use" Permission
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (fix version 1.3.2):
Fixed in Mobile Notifications 1.3.2 which is available from 2019.4.0f1