Search Issue Tracker
Fixed in 2023.1.0b9
Fixed in 2023.1.X, 2023.2.X, 2023.2.0a6
Votes
0
Found in
2023.1.0b3
2023.2.0a1
Issue ID
UUM-26386
Regression
No
[IL2CPP][MacOS] Build fails with System.ArgumentException when building with IL2CPP stack trace information with line numbers
How to reproduce:
1. Create a new Unity project
2. Edit -> Project Settings -> Player -> Other Settings -> Scripting Backend -> IL2CPP
3. IL2CPP Stack Trace information -> Method Name, File Name, and Line Number
4. File -> Build Settings -> Check "Development build"
5. Press "Build"
Expected result: Player is built with no errors
Actual result: Player is built with "System.ArgumentException: Another action is already registered for" error
Reproducible with: 2023.1.0b3, 2023.2.0a1
Could not test with: 2020.3, 2021.3, 2022.2 (No "IL2CPP Stack Trace information" setting)
Reproduced on: MacOS 12.0.1 M1 Max, Mac Intel
Wasn't reproduced on: Windows 11
Error:
Internal build system error. BuildProgram exited with code 1.
System.ArgumentException: Another action is already registered for /Users/username/Downloads/project/Library/Bee/artifacts/MacStandalonePlayerBuildProgram/il2cppOutput/build/il2cpp.usym
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
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Resolution Note (fix version 2023.2):
Fixed in: 2023.2.0a6
Resolution Note (fix version 2023.1):
Fixed in: 2023.1.0b9