Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4.10f1
2021.1
Issue ID
1283955
Regression
No
[iOS] Social.localUser.Authenticate() is not called when user is not authenticated and GameCenter login pop-up is dismissed
How to reproduce:
1. Open the attached 'New Unity Project.zip' project
2. Switch Platform to iOS in Build Settings
3. Build for iOS and open the Xcode project
4. Deploy Xcode project to an iOS device without being logged into GameCenter
5. Click on the Authenticate button on the screen
6. Observe that the following message is displayed 'SocialAuthenticateAsync is called'
7. If popup from GameCenter opens and wants you to log in, dismiss it
8. See the message that is called from the GameCenterLogin script in Unity: SOCIAL SIGN IN ERROR
9. Hit the authenticate button again
Actual result: 'SocialAuthenticateAsync called' message is displayed, pop-up window of Game Center does not appear
Expected result: 'SocialAuthenticateAsync' and 'SOCIAL SIGN IN ERROR' errors are being thrown
Reproducible with: 2018.4.29f1, 2019.4.13f1, 2020.1.9f1, 2020.2.0b7, 2021.1.0a1
Reproducible with:
iPhone XR (iOS 13.4.1)
iPad 9.7’ 6th gen (iOS 14.2)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2020.2.X):
On certain platforms (including but not limited to iOS and tvOS), the callback is only invoked on the first call to Authenticate(). Subsequent calls to Authenticate() on such platforms results in no callback being triggered. This can occur if, for example, the user or the OS cancels the authentication operation before it has completed. Please ensure you test for this situation.