Search Issue Tracker
Not Reproducible
Votes
0
Found in
6.3.1
6.4.1
Issue ID
UUM-131167
Regression
No
“ExecutionFailedException” error is thrown when building AR Mobile Template using iOS Platform
Steps to reproduce:
1. Create new Unity project using AR Mobile Template
2. Open Build Profiles window
3. Switch active Platform to iOS
4. Press “Build”
5. Once project is built, observe the Console window
Actual results: Error “ExecutionFailedException: Execution of actool failed with exit code 1. stderr:” is thrown after building project using iOS Platform
Expected results: No errors thrown after building project
Reproducible with versions: 2.1.1 (6000.0.64f1, 6000.2.15f1, 6000.3.1f1, 6000.4.0b1)
Can’t test with versions: 6000.5.0a1 (Template not available)
Tested on (OS): macOS Tahoe 26.1 (M1), Intel
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
- 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
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.