I just got this on iOS (iPhone 7 Plus) so it's not an issue with Windows. Tried all the troubleshooting recommended here.
It's not my phone - I can play other MS games and sign in on Xbox app without issue.
As MS tries to push blame the consumer, it's clear from these responses that it's on their end.
I just resolved this issue on my device. The device I am using is:
Device: Nokia 6.1 (Android)
Android Version: 8.1.0
Android security patch level: 1 August, 2018
Issue:
-Today, 4 Sept 18, I received an error code 121003, that Solitaire failed to download my progress from the cloud. This affected the daily challenges I completed, and the Star Club.
First attempts at fixing the action:
-Removed and re-installed Solitaire, this did not fix the issue.
-Removed and re-installed the Android Xbox app, and removed and re-installed Solitaire, this did not fix the issue.
-Rebooted phone, this did not fix the issue.
-Shut down phone for 30 minutes, and start it back up. This did not fix the issue.
From my gut, there is a different server that manages the information for the Solitaire app that is not linked at all to the Xbox Live servers. Also, the Solitaire application does not have any dependencies on the Xbox mobile application. As I found with
my solution.
In order to determine if the issue is with my device, or with the servers that maintain my Solitaire profile, I factory reset my phone.
After factory resetting, I re-installed Solitaire (not re-installing the Xbox App), signed in, and all my progress returned. My daily challenge and Star Club progress was restored.
In the end, there was something going on with my device, not the Solitaire servers. If the issue was with the Solitaire servers, then factory resetting my phone would not have fixed the issue. To find out exactly
why this error occurs, I would need the issue to appear again, set my phone to developer mode, and look into the device from a Software Engineering standpoint.
For now, if all else fails, a factory reset very well may work.
Sorry you typed this all out - it was indeed a server side issue with MS yesterday, not my device (nor yours, I'm guessing)