Search Issue Tracker
Not Reproducible
Votes
0
Found in
2022.1.0b7
Issue ID
1403973
Regression
No
[Apple Silicon] UAAL example fails to build for Android with IL2CPP on M1 macOS devices
Steps to reproduce:
1. Get the UAAL example project from https://github.com/Unity-Technologies/uaal-example
2. Open the UnityProject
3. Change `Scripting Backend` to `IL2CPP`
4. Continue with the Android instructions to set up Unity as a Library for Android fully (https://github.com/Unity-Technologies/uaal-example/blob/master/docs/android.md)
5. Once everything is set up and Android Studio project is synced, try building the project
Expected result: Android Studio build succeeds and can be deployed to device.
Actual result: Android Studio build fails with the error: "Your project contains C++ files but it is not using a supported native build system."
Notes:
Doesn't reproduce on Intel macOS devices.
Exporting simple Gradle project and building it with Android Studio works just fine on M1 MacBook if it doesn't use UAAL integration.
Reproduced with: 2022.1.0b7, 2022.2.0a4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment