Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b11
Issue ID
960802
Regression
No
[Xcode] Team is not being selected automatically when "Automatically manage signing" is selected
To reproduce:
1. Create an empty project
2. Build it for iOS
3. Open build project in Xcode
4. General > Signing > Team and make sure that Automatically manage signing is checked
5. Notice that Team wasn't selected automatically (is set to None)
Expected result: Team should be chosen automatically.
Reproduced with: 5.6.4p1, 2017.2.0f3, 2017.3.0b6, 2018.1.0b6
Xcode Team option will be chosen when Unity Player Setting will have:
- Automatically Sign [X] checked ( this option corresponds to Xcode Targets/General/Signing/Xcode Automatically manage signing option, responsible for provision profile,app IDs,entitlements )
- Automatic Signing Team ID is set to valid 10-character string ( this option corresponds to Xcode Targets/General/Signing/Team, and should be set in Unity or otherwise selected in Xcode. Also do not confuse Team Name that is visible in Xcode and Team ID that is expected in Unity )
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
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not always matching search term correctly
- Crash on memcpy when opening a project that loads TSS files
jedla22
Jul 24, 2019 08:16
O still see this problem in Unity 2019.1.0f2 for Mac. The workaround JMCALLISTER_ZOSMAY works well. But still, it will be nice to fix this in Unity. It takes me a couple of hours before I figured out what is going wrong :(
hazel_koop
Jul 04, 2019 17:48
Happening for me too, the workaround in the forum post resolved it (for now). Not sure what "by design" could mean in this context??
jmcallister_zos
May 08, 2019 12:18
Ran into this issue (2018.3.7f1) and also found a forum post describing the same problem.
https://forum.unity.com/threads/automatically-sign-option-is-ignored-when-exporting-project-on-other-machine.599548/
Posted our findings on that thread and a workaround to the problem.
I do not think this issue should be closed as designed based on the findings I posted in the forum thread.
Unity creates an incomplete plist at launch if the plist does not already exist. While options in the UI, like Automatically Sign, appear to be checked they are not honored during the generation of the Xcode project. To put the plist into a correct state you can change any Unity preference (for example uncheck and recheck the automatically sign checkbox) and close Unity, it will then save a more complete plist which will result in the expected Xcodeproj being generated.
markheps
Feb 28, 2018 09:02
We seem to be seeing this behaviour internally on one mac out of seven