-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading a SaveGame file on iOS occasionally gets stuck indefinitely #163
Comments
I'm looking at the code, I don't see a path where we don't return result, if we get error we return an error, if we get result we return the results.
|
Can you use version 4.0.2 and share the logs? |
For me, the first session always crashes indefinitely, but it works normally from the second session onwards. |
Hi @Abedalkareem, sorry I've been busy and my temporary workaround is doing fine @thize seems to be able to reproduce it reliably. Can you please share logs like @Abedalkareem asked? |
I have been unable to reproduce the issue. The only thing I can track down is a duplicate If you are still experiencing or can recreate the issue, please try the same code after pulling the potential hotfix to see if it resolves your problem. Update your games_services: # 4.0.3
git:
url: https://github.com/Abedalkareem/games_services.git
ref: gc-duplicate-sign-in-fix
path: games_services |
Flutter version 3.22.2 (stable)
games_services: 4.0.1
iOS 16.5.1
Game center sign in and cloud saves are functioning as expected on iOS. I only run SaveGame methods after a successful sign in. But in about one in 30 launches
will get stuck indefinitely, with no error thrown, no logs for me to inspect.
I've tried checking all logs on the iPhone's console, restarting the app, restarting the phone in such a case. There's unfortunately not much I can do to debug this further.
The only thing that seems to fix this right now is reinstalling the app.
My current workaround is to wait 5 secs for response otherwise proceed assuming an empty response.
Any help appreciated :)
The text was updated successfully, but these errors were encountered: