You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We know this is an issue with logins, please stop spamming the issue with "same here" with no actual information on helping trying to fix it. It's unhelpful and it clutters issues with fluff.
I dug into this one with debug logging on plumesign account login (macOS, v2.7.2 + mac-ani.jkcoxson.com). Findings so far:
What actually fails
SRP itself succeeds, but GSA answers au = "secondaryAuth", so we go down the SMS path.
GET https://gsa.apple.com/auth (trusted phone numbers) returns 403 with an empty body, and then PUT /auth/verify/phone also returns 403 with an empty body. It's not just SMS: every gsa.apple.com/auth* call is rejected after login.
Changing the 2FA User-Agent (Xcode vs akd/...) or the 2FA client info (akd vs dt.Xcode) makes no difference.
Reverting to the v2.7.1 identity (iTunes Windows client info + ani.sidestore.app) now fails earlier with -27952 Update iCloud for Windows, so going back isn't an option.
Likely cause
mac-ani.jkcoxson.com/v3/client_info advertises <MacBookPro13,3> <Mac OS X;10.12.6;16G29>. Since mid-October Apple seems to reject this outdated identity on the /auth endpoints. SideStore is tracking the same 403 on SMS (SideStore#1683 ports SideInstaller's workaround): when the server advertises macOS < 10.13, they substitute a current Mac identity (<MacBookPro18,3> <macOS;26.6;25F84> <com.apple.AuthKit/1 (com.apple.akd/1.0)>, UA AuthKit/1 (Macintosh; OS X 26.6) (com.apple.akd/1.0)), and on a 2FA 403 they fall back to a code generated on a trusted device instead of failing.
Small bug found along the way
AnisetteData::get_header lowercases header values, not just keys, so the SRP X-MMe-Client-Info is sent as <macbookpro13,3> <mac os x;10.12.6;16g29>. Probably not the root cause, but worth fixing.
Next
I have a branch with the get_header fix, a trusted-device-code fallback on 2FA 403, error bodies included in the 2FA error messages, and the SideInstaller-style identity substitution. I'm waiting out a GSA 429 rate limit before testing. I'll open a PR if it works.
Activity
shant1010 commentedon Oct 24, 2026
claration commentedon Oct 24, 2026
We know this is an issue with logins, please stop spamming the issue with "same here" with no actual information on helping trying to fix it. It's unhelpful and it clutters issues with fluff.
If you want this to be fixed, send patches!
Antholife commentedon Oct 27, 2026
I dug into this one with debug logging on plumesign account login (macOS, v2.7.2 + mac-ani.jkcoxson.com). Findings so far:
What actually fails
Likely cause
Small bug found along the way
Next
I have a branch with the get_header fix, a trusted-device-code fallback on 2FA 403, error bodies included in the 2FA error messages, and the SideInstaller-style identity substitution. I'm waiting out a GSA 429 rate limit before testing. I'll open a PR if it works.
Antholife commentedon Oct 30, 2026