Search Issue Tracker
Fixed in 2.0.0
Votes
1
Found in [Package]
1.4.2
Issue ID
1376849
Regression
No
[Android][Mobile Notifications] Cannot Build directly to Android 12 with Mobile Notifications
Reproduction steps:
1. Create a new project
2. Install Mobile Notifications package
3. Switch to Android and make sure SDK 31 is selected
4. Build and Run on Android 12
Expected result: APK is installed and launched on Android 12
Actual result: APK is not installed and launched on Android 12
Reproduces on: Mobile Notifications 1.0.2 - 1.4.2 (2020.3.23f1, 2021.2.2f1, 2022.1.0a15)
Could not effectively test on 2019.4.32f1 since I get errors regardless if Mobile Notifications is installed or not
Reproduces with these devices:
VLNQA00263 - Google Pixel 3 (Pixel 3), OS: 12.0.0, CPU: Snapdragon 845, GPU: Adreno 630
Does not reproduce with these devices:
VLNQA00318 - OnePlus 7 Pro (GM1913), OS: 9.0.0, CPU: Snapdragon 855 SM8150, GPU: Adreno 640
VLNQA00231 - HUAWEI Mate 20 Pro (LYA-L29), OS: 9.0.0, CPU: HiSilicon Kirin 980, GPU: Mali-G76
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Notes:
-android:exported is defined in the Android Manifest
-Issue only reproduces if Mobile Notifications is installed
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
- “FocusController has unprocessed focus events.” warnings are thrown after adding iOS, tvOS or visionOS Build Profiles
- Holes and different colors appear on default Tree Materials after applying them to the Tree GameObject and undoing changes
- Error indicating that the Text Asset Importer hasn't been disposed properly is logged when switching Importer Type in a Focused Inspector
- Documentation installation shows "Install failed: Validation Failed" when installing Android Build Support module
- Error indicating that the Package Manifest Importer hasn't been disposed properly is logged when switching Importer Type in a Focused Inspector
Resolution Note (fix version 2.0.0):
Fixed in Mobile Notifications 2.0.0