Search Issue Tracker
By Design
Votes
0
Found in [Package]
2.2.0
Issue ID
MNB-58
Regression
No
UnityNotificationManager.java:164: error: cannot find symbol error when targeting SDK API lower than 33 with Mobile Notifications
Steps to reproduce:
1. Open the attached user's project
2. Make sure the SDK path in External Settings points toward Android Modules installed via HUB
3. Set the "Target SDK level" to 32, 31 or 30
4. Build for Android
5. Observe console error
Expected behavior: Build success
Actual behavior: build fails
Reproducible on: Mobile Notifications 2.2.0 (2021.3.28f1, 2022.3.4f1, 2023.1.4f1, 2023.2.0a23)
Not reproducible on: Mobile Notifications 2.1.1 (2021.3.26f1, 2022.2.21f1, 2023.1.0b18, 2023.2.0a16)
Notes:
-Console error:
UnityNotificationManager.java:164: error: cannot find symbol
if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU)
symbol: variable TIRAMISU
location: class VERSION_CODES
-Workaround is to set the Target SDK level to 33
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
- 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
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
Resolution Note:
Mobile Notifications require SDK 33 to compile the code.
By default Unity set compile SDK to the same as target SDK. This can be altered by using custom gradle template:
- Enable Custom Main Gradle Template in Player Settings (Publishing)
- Open the template file in text Editor and modify compileSdkVersion to 33 instead of default **TARGETSDKVERSION**
Also note, that from August 31 Google Play will require to target SDK 33 for all new apps and app updates, so if you plan to publish anything after that date, set target SDK to 33:
https://developer.android.com/google/play/requirements/target-sdk