[TEMPORARY FIX] SideStore iCloud Sign-in Errors (-80045, -22411, 503 Temporarily)

[wuaan204]

Hi everyone!

As many of you may know, the SideStore community is currently experiencing iCloud sign-in issues with these common error codes:

• -80045
• -22411
• 503 Temporarily

I accidentally discovered a workaround that worked for me, so I thought I'd share it here. Please follow the steps carefully.

Prerequisites

1. A Windows PC and an iPhone.
2. Both devices should be connected to the same Wi-Fi network.
3. Download and install the latest version of LocalDevVPN and keep it connected throughout the process.

Part 1: Install SideStore using AltStore

1. Open AltStore on your PC.
2. Sign in with your Apple ID and connect your iPhone.
3. Install the latest SideStore Nightly IPA.
4. Once installed, open SideStore on your iPhone and complete the initial setup.

A little explanation: I used a different Apple ID (notLoginAcc) to install SideStore because my main Apple ID (loginAcc), which was already signed in on my iPhone, had reached its app limit (10/10).

Using a different account was simply my workaround for the installation limitation, NOT a requirement for this sign-in fix. The interesting part came later!

Part 2: Place Pairing File

1. Download idevice_pair v1.1.0 - Platform fixes.
2. Open idevice_pair, connect your iPhone to the PC and select your device.
3. Under the "Pairing file" option, select Remote Pairing (because we installed Nightly in Part 1).
4. Click the small Create button to generate the pairing file.
5. Export the generated pairing file to your PC.
6. Upload the pairing file to a cloud storage service (Google Drive, for example).
7. On your iPhone, download the pairing file and save it to the Files app.
8. Open SideStore. When the pairing file import prompt appears, manually select the pairing file you just downloaded to complete the pairing process.

Part 3: Sign-in

1. Go to:

   Settings > User Customizations > Anisette Client Configuration > Interactive

2. Replace the two default values with:

   Client Info:

   <PC> <Windows;6.2(0,0);9200> <com.apple.AuthKit/1 (com.apple.iTunes/12.12.4.1)>
   

   User Agent:

   akd/1.0 CFNetwork/808.1.4
   

3. Scroll down and click Save Overrides.

4. Completely close SideStore from the app switcher and reopen it.

5. Now try signing in with your Apple ID.

What happened in my case?

Initially, I tried signing in with notLoginAcc (the account I used to install SideStore).

• It showed the verification options.
• I selected SMS verification.
• But SideStore returned Cannot connect to iCloud.

Then I tried signing in with loginAcc (the account already signed in on my iPhone).

And BOOM! IT WORKED!

I actually received the 6-digit verification code, entered it into SideStore, and successfully authenticated my account.

OMG, finally!

I don't know exactly why this worked, and I haven't tested it with other devices or accounts yet. But since it worked for me, I hope it helps some of you too.

If you try this method, please share your results!

[oasoobi]

I was having trouble with a 503 Temporarily Unavailable error, but your solution worked!

[wuaan204]

upvote my share bro haha

[yumahayes]

If you're having trouble signing in with your Apple ID in SideStore, there's no need to install SideStore separately via AltStore. This is an issue that with which anisette server to use when signing in. Follow the steps below to fix this.

(1) Turn-off "On-device Anisette"

SideStore > Settings > User Customizations > ANISETTE > On-Device Anisette

• This would show a prompt message to restart the app, so re-open the SideStore app directly or from LiveContainer depending on your environment.
• Leave "Anisette Client Configuration" as it is. No need to make changes to this.

(2) Choose appropriate Anisette server

SideStore > Settings > Anisette Servers > Available Servers

• By default, "SideStore (https://ani.sidestore.io)" is selected but this will likely cause the problem. "SideStore (New) (https://new.ani.sidestore.io)" is not stable at the moment either.
• If you have the latest version of iloader (version 2.3.10) you can kind of "pre-test" with which anisette server you can sign in with your Apple ID. In my case, I use Mac so picked "jkcoxson (Mac)" and confirmed it worked.
• Back to the SideStore and choose the server that works. Again, "jkcoxson (https://mac-ani.jkcoxson.com)" is my choice and if you're a Mac user you should choose the same.

(3) Sign-In with your Apple ID

SideStore > ACCOUNT > Sign in with Apple ID

• Fill out your ID/Pass and click on "Sign In"

[yumahayes]

Are you being asked to enter 6-digits verification code when signing in? I do not think you need to actually log in with the Apple ID to use on neither the target device (i.e., iPhone) nor the source device (i.e., Mac/PC that sideloaded SideStore into your target device). In fact, I am using an ID that I only use for SideStore and avoid using my primary Apple Account just in case the ID gets banned for some reasons.

Further more, I would enabling the following logging options for troubleshooting:

SideStore > Settings > Developer Options > Logging & Diagnostics

• "SideSign Verbose Logging"

SideStore > Settings > Developer Options > Logging & Diagnostics > Operations Logging Control > Standalone Steps

• "Sign In"

After enabling these more detailed information will be traced in Console Log (Settings > View Error Log > Click on the console icon on top right corner).

[so-5699]

Thanks for your reply!

I also use a sub-account for sideloading. Since I don't have any devices signed in with this sub-account, I select SMS for two-factor authentication (2FA).
In this case, without prompting me for the 6-digit verification code, the login fails with the error "Could not connect to iCloud".

Furthermore, when I try to log in with this sub-account on the official Apple website, it displays the error: "Unable to verify. A verification code cannot currently be sent to this phone number. Please try again later."

[wuaan204]

you can try my method

[yumahayes]

It's very interesting that it failed to logging into Apple's own website (I assume "account.apple.com" ?).

At this point, it maybe worth giving it a try with rewriting the client information method explained in Part 3 in the OP's post.
Please let me know if that workaround fixed the problem. I'm keen to figure out the root cause of the issue especially in your case scenario.

[so-5699]

I’ve already tried modifying the client information several times, and my main account has already successfully authenticated with SideStore using a different method.

What I am trying to achieve now is logging into SideStore with a sub-account. However, the process is stuck with the error "Could not connect to iCloud", which I suspect is caused by an SMS issue.

[so-5699]

[yumahayes]

To replicate your issue, I have newly created another Apple account from https://account.apple.com/ and use it for sign-in in SideStore. Though if you have certificate stored with the previous Apple account you'd need to resign it to fix the conflict, in short everything worked fine at my end. The only strange behavior I saw was that after entering verification code and sign-in for the first attempt it did not work, however, I have sent another code via SMS and using that code and sign-in again did work out fine.

For now, if you want to use your sub-account, my recommendation would be to create a new Apple Account and use that instead of the one which never worked for you. Hope this helps.

[yumahayes]

One more thing. If you're using Gmail address to set up Apple account, you might not be able to use email alias (i.e. +@gmail.com to set up a new account. For instance, if you already have "user12345+sidestore@gmail.com" associated with existing Apple account, you will not be create another account using "user12345+sidestore2@gmail.com" as both email addresses are essentially the same. In order to create a new Apple Account, just use a fresh email address that has not been associated with any Apple account.

[so-5699]

Thank you very much for your kind and detailed assistance.
I will set up a new sub-account using a new number and give it a try.

[PranavDupati]

People, this is the error I'm getting. Any help? I did the steps above.

[wuaan204]

you mean my steps ??

[Duoyiduo1]

After the change, I can receive the verification code when logging in, but I get error -80046 after entering it.

[kielbad]

me too

[wuaan204]

have you tried my method yet ?

[kielbad]

Yes! Before your method I got error 80045. Now I can receive the code, but after entering it I'm blocked by error 80046 and still can't sign in. Any suggestions?

[nagisa77]

same

[Duoyiduo1]

I’ve restored all the previous changes I made to the user agent back to the default. That means I just turned off the on-device anisette in the app’s default state, then after selecting the seventh one from the Anisette Servers, I reopened the app and logged in successfully. I don’t even understand why the server caused it or whatever, but anyway, it’s finally solved. I used the SS+LC version and solved 80046 using this method.

[TheNightmanCodeth]

I was getting

Your Apple ID can only be used on devices running iOS 16.2 or later, or macOS 13.1 or later...

This configuration fixed it for me:

Anisette Server: https://mac-ani.jkcoxson.com
Client Info: <MacBookPro13,3> <Mac OS X;27.2;26B118> <com.apple.AuthKit/1 (com.apple.akd/1.0)>
User Agent: akd/1.0 CFNetwork/811.5.4 Darwin/16.7.0

I think this was on account of the new ADP on apple accounts. Not on-device anisette does not work even with those client settings.