Search Issue Tracker
Fixed
Fixed in 2.3.2
Votes
0
Found in [Package]
2.3.1
Issue ID
MNB-76
Regression
Yes
[Android] "Schedule at exact time" set to "Nothing" is being ignored and "SCHEDULE_EXACT_ALARM" permission is being added to the "AndroidManifest.xml" file when building the project for Android Platform
How to reproduce:
1. Open the "IN_65077" project
2. In the Build Settings enable “Development Build”
3. Press Build
4. In the Android Studio press Build -> "Analyze APK..."
5. Select the built APK
6. In Android Studio open the "AndroidManifest.xml" file
7. Observe the given permissions
Expected result: "SCHEDULE_EXACT_ALARM" permission is not added
Actual result: "SCHEDULE_EXACT_ALARM" permission is added
Reproducible with: 2.3.0, 2.3.1 (2021.3.34f1, 2022.3.17f1, 2023.2.5f1, 2023.3.0b2)
Not reproducible with: 2.2.2 (2021.3.34f1, 2022.3.17f1, 2023.2.5f1, 2023.3.0b2)
Reproducible on: Windows 10 Pro
Not reproducible on: No other environment tested
Notes:
- Also reproducible on the new project
- Didn’t test on the iOS and Windows Standalone Platforms because the setting "Schedule at exact time" is for the Android Platform
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Add comment