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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Add comment