Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
2
Found in
2018.3.0b7
2018.4.0f1
2019.1.0a5
2019.2.0a1
2019.3.0a1
Issue ID
1156958
Regression
No
[IL2CPP][macOS] IL2CPP fails to link debug symbols when build name has spaces
How to reproduce:
1. Create a new project
2. Go to File > Build Settings > Player Settings
3. Go to Other Settings > Configuration and change Scripting Backend to IL2CPP
4. Build the project with a name that includes spaces
Expected result: build completes without errors
Actual result: build completes with the "fails to link debug symbols" error
Reproducible with: 2018.4.3f1, 2019.1.8f1, 2019.2.0b7, 2019.3.0a7
Notes:
- Could not reproduce in versions 2018.3.0b6 and 2019.1.0a4 and earlier as building failed due to unrelated error.
- Reproducible only on Mac.
- Couldn't test on 2017.4 as IL2CPP is unavailable.
-
edientexam
Apr 11, 2024 08:56
Obtain a name for the project that contains spaces and construct it.
-
HatInACat
Apr 07, 2022 14:44
I am seeing this exact issue in 2020.3.31f1, while building for Linux, IL2CPP fails to link if the build name has a space in it.
-
_Adriaan
Mar 15, 2020 18:00
Seeing this issue in 2019.3.5f1.
-
BurningthumbStudios
Feb 08, 2020 18:20
I just started getting this problem on a project that used to work. The difference is I added In-App purchase.
-
JBPrime
Sep 28, 2019 16:51
Still occurs in 2019.2.3f1.
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
- Rigidbody2D.Slide API does not have the needed configuration when creating a 2D Top-Down character controller
- Opening reference for "Playables"component redirects to a missing page
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
Resolution Note (fix version 2019.4):
Fixed in 2019.4.15f1