GamesClientStatusCodes.SNAPSHOT_CONTENTS_UNAVAILABLE status code returned when opening save backing about android-basic-samples HOT 15 OPEN

Can you share your game package name, please?

from android-basic-samples.

In regards to the cases count, do you have the same stats but for number of affected users per day?

from android-basic-samples.

The package name is com.concretesoftware.pbachallenge_androidmarket

As for affected users per day:
July 10th: ~5 users per day
July 23rd: ~100 users per day
July 30th: ~600 users per day
It seems like these same users are being affected day-after-day.

from android-basic-samples.

Thank you, @JoeyRosicka.

from android-basic-samples.

Update on our end - still these same ~600 users who are getting SNAPSHOT_CONTENTS_UNAVAILABLE when attempting to retrieve their save snapshot. The documentation on this notes to "See the device logs for more details" and we have been able to take a look at some logcats, but we are not seeing anything related to the error.

It's been tough to find any additional information on SNAPSHOT_CONTENTS_UNAVAILABLE. Are there any notable situations where this error occurs?

from android-basic-samples.

@JoeyRosicka, thank you for the update.

Are there any notable situations where this error occurs?
Usually this code should be returned only if user lost the Internet connection while snapshot BLOB download.

We are investigating the issue on the Play Service side.
Would it be possible to share logcats/bugreports with us? Preferably link to a Google Drive folder but, please, don't accept access request unless it from @google.com email addresses.

from android-basic-samples.

@smile616 here is a logcat from one of the affected users - I'll grant access when I see a request. https://drive.google.com/drive/folders/1kM-LysGy4xL6jcKujJAELAcVCmZNPBXz?usp=sharing

Also this is probably implied, but just in case I'll note that this is a high-priority issue for us since we have a lot of users unable to access their save data. Thanks for continuing to look into this.

from android-basic-samples.

Thank you, @JoeyRosicka. Access request sent.

from android-basic-samples.

@JoeyRosicka
We've applied some steps on the Play Service side that should mitigate the error rate.
I keep the issue open for monitoring.

from android-basic-samples.

Thanks, very good to hear.

from android-basic-samples.

It looks like the error rate has dramatically decreased since August 10th which appears to line up with when you reporting your change on the Play Services side. Now seeing 5-10 users affected per day rather than hundreds.

from android-basic-samples.

Thank you, @JoeyRosicka, for the update.

from android-basic-samples.

No problem @smile616. Please let me know if there's anything we can do to help get the error rate down to 0.

from android-basic-samples.

Hi @JoeyRosicka, unfortunately, there is nothing can be done on your side. We expect that the error rate will reduce to 0 organically by mid September.

from android-basic-samples.

Alright, thanks for the update.

from android-basic-samples.