Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.4f1
Issue ID
1245194
Regression
No
[iOS] ProjectCapabilityManager.AddSignInWithApple adds AuthenticationServices framework for the wrong target
Steps to reproduce:
1. Open the attached project (pbxproject-api-test.zip)
2. Switch to iOS and make a build
3. Open Xcode project
4. Notice that 'Sign In With Apple' capability is added correctly to Unity-iPhone target
5. Try to build the Xcode project
Actual behaviour: Build will fail because AuthenticationServices.framework is added to Unity-iPhone target.
Expected behaviour: AuthenticationServices.framework that is needed by 'Sign In With Apple' capability should be added to UnityFramework target.
Notes:
This can be worked-around by adding AuthenticationServices.framework to UnityFramework target manually.
Only affects versions that have UAAL implemented (2019.3+), because before that, only one target was used.
Reproduced with:
2019.3.4f1, 2020.1.0b8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Up, Down and other Buttons in a Style Sheet's Inspector unselect items when they are clicked while they are disabled
- Virtual Player remains active and still launches when removed from Additional Editor Instances from a custom Play Mode Scenario
- UI Toolkit Editor Window Creator becomes not interactable and greyed out when a long name is entered
- [Web][iOS] Web Player keeps restarting on launch when Native C/C++ Multithreading is enabled
- "Add Scene to Scenes in Build" pop-up reappears after Scene has already been added and another Multiplayer Editor Instance is loaded
Add comment