Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.3.14f1
Issue ID
1254117
Regression
No
[iOS] Plugin "Compile Flags" do not update on Append Build
Changes to native source "Compile flags" are not respected
1. Build the attached project for iOS
2. Go to TARGETS > UnityFramework > Build Phases > Compile Sources > Test.m.
3. Note the compile flag -DPLUGIN_IMPORTER_COMPILE_FLAG is set
4. Change the compile flags on Test.m to something else, e.g, "-DSOMETHING_ELSE"
5. Build again (CMD + B)
6. Note the compile flags is still set to -DPLUGIN_IMPORTER_COMPILE_FLAG
Note: If you instead rebuild from scratch (i.e., "replace") the trampoline project, the new compile flag is set correctly.
Expected behavior: The "compile flags" are updated each time the player is built.
Actual behavior: The "compile flags" are only used once, the first time the trampoline project is generated.
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 (fix version 2020.2):
Fixed in 2021.1.0a9.1547