Closed ChrisNZL closed 1 year ago
Further report, 0.3.6c, feedback ID 20221009-NPY7S
My weapons progress keeps getting reset!
Log is showing:
6:33:41, Frame 816, WARNING » WARNING: CloudOnce failed to reveal achievement: Native API failed to reveal achievement ReachRoom10_Singleplayer (ReachRoom10_Singleplayer). Cause unknown.
[[[ ^ REPEATING MESSAGE... ]]]
6:33:41, Frame 816, WARNING » WARNING: CloudOnce failed to reveal achievement: Native API failed to reveal achievement AcquireLoot_Weapon_Rarity4 (AcquireLoot_Weapon_Rarity4). Cause unknown.
[[[ ^ REPEATING MESSAGE... ]]]
6:33:41, Frame 816, WARNING » WARNING: CloudOnce failed to reveal achievement: Native API failed to reveal achievement AcquireLoot_Shield_Rarity4 (AcquireLoot_Shield_Rarity4). Cause unknown.
[[[ ^ REPEATING MESSAGE... ]]]
Cause unknown.
, reported by CloudOnce, isn't very helpful.
Kind of related but not really:
Different iOS report, 0.3.6c, feedback ID 20221010-JBCWN
If an achievement has already been earned, the "Cause unknown" warning gets logged:
6:02:39, Frame 935, WARNING » WARNING: CloudOnce failed to reveal achievement: Native API failed to reveal achievement ReachRoom10_Singleplayer (ReachRoom10_Singleplayer). Cause unknown.
6:02:39, Frame 935, LOG » TaskProgressManager.SubmitTaskProgress: Task ReachRoom10_Singleplayer is completed (earned).
6:02:39, Frame 935, LOG » TaskProgressManager.SubmitTaskProgress: Task ReachRoom10_Singleplayer has not been fully uploaded this session. Submitting now...
Bugs with the startup Achievement / Progress sync is definitely an issue.
Feedback ID: 0.3.6C_20221017-H8GW3
Logs do not show any errors or warnings, nor attempts to sync progress from Google Play.
Confirmed myself from testing with Google Play and 0.3.6c:
0.3.7:
Fixed startup sync issue for saved games, achievement progress, and account file. Syncing should happen more reliably now (can take a couple seconds after user signs in typically).
Added a "Cloud Sync" item within the Account tab so player can manually force a sync if desired:
Manual report from iOS, 0.3.6c (feedback ID
20221007-ZQW3R
), across two devices:Additional report, feedback ID
0.3.6C_20221011-FMSJG
– no errors or warnings in the log files.Possible causes:
Tasks: