Search Issue Tracker
Fixed in 5.5.0
Votes
4
Found in
4.5.5f1
Issue ID
643923
Regression
No
If Social.localUser.Authenticate fails it doesn't return a reason why it failed
After Social.localUser.Authenticate fails, it should output/return why it failed, for example it might be necessary to react differently to situation when the user doesn't login to the Game Center by exiting login window, than when Authenticate fails for other reasons. But because it only returns a bool it's impossible to determine the actual reason.
To Reproduce:
1. Just build the scene 'TestScene(Standalone)' from the attached project.
2. When Authenticate there is now way to determine why exactly did it fail.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment