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
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
Add comment