Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2020.3
2021.1
2021.2
2022.1
2022.1.0a8
Issue ID
1367588
Regression
No
[ChromeOS] When Patch and Patch And Run build options are used there is no clear error message why the build fails
How to reproduce:
1. Create a new project
2. Open the Build Settings and switch the Target Platform to Android
3. Enable the Development Build option
4. Open the Player Settings window
5. Under the Other Settings tab switch the backend support to IL2CPP and enable the Chrome OS build support (x86/x86-64)
6. In the Build Settings window select a ChromeOS device in the Run Device drop-down menu (If it is not listed connect via wifi and ADB command)
7. Click "Patch" or "Patch And Run"
Expected results: When the build process fails an error message is thrown informing that "Patch" or "Patch And Run" option is not supported on the Chome OS platform
Actual results: Build error messages are thrown, but there is no clear explanation on what exactly is failing
Reproducible with: 2020.3.19f1, 2021.1.22f1, 2021.2.0b13, 2022.1.0a8
Could not test with: 2019.4.30f1(Chrome OS support is not yet available)
Notes:
1. This issue can be identified by inspecting the Detailed Log in the error message which informs about failed deployment to the target device. One of the last entries in the log should be - "run-as: run-as is disabled from the kernel commandline". The built Player will also throw a "Failed to load 'libmain.so'" error on launch
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
Add comment