fix: update GrandSlam client info header to fix HTTP 503 error - #247
Open
shahbajjamil wants to merge 4 commits into
Open
shahbajjamil wants to merge 4 commits into
shahbajjamil wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the `503 Server Error: Service Temporarily Unavailable for url: https://gsa.apple.com/grandslam/GsService2\` encountered during initial authentication and device registration.
Fixes #245
Fixes #246
Root Cause
Starting in September 2026, Apple's edge firewall began rejecting any GrandSlam requests whose `X-MMe-Client-Info` header references `com.apple.dt.Xcode` (such as `<com.apple.AOSKit/282 (com.apple.dt.Xcode/3594.4.19)>`). The request is immediately rejected at the edge with an HTML `503 Service Temporarily Unavailable` response before reaching the GSA service or evaluating credentials.
This same issue was identified and resolved upstream in malmeloo/FindMy.py#271.
Changes Made
Verification & Testing