Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
0
Found in
2018.4
2019.4
2019.4.24f1
2020.3
2021.1
2021.2
Issue ID
1335997
Regression
No
globalgamemanagers.assets contains references to platform-specific scripts when those scripts are present in the Project
Reproduction steps:
1. Open the attached project "newTest.zip"
2. Select "Assets/Android/AndroidScripts.asmdef" in the Project window
3. In the Inspector, ensure the Platforms are set to different ones than the current Build Platform
4. Build the Project
5. In the Build folder, find and open "globalgamemanagers.assets" as a text file
6. Search for "AndroidScript" in the file
Expected result: the string "AndroidScript" is not found within the file
Actual result: the string "AndroidScript" can be found in the file
Reproducible with: 2018.4.35f1, 2019.4.26f1, 2020.3.8f1, 2021.1.7f1, 2021.2.0a17
Notes:
- This issue at the moment is most relevant to Apple Platforms since it causes the App being rejected from the Apple Store due to references to platform-specific filenames
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2021.1):
Fixed in 2022.1.0a1
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b11
Resolution Note (fix version 2021.1):
Fixed in 2021.1.18f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.17f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.30f1