Friday, October 3, 2025

Difficulty with account.apple.com – Privateness Consent and Account Migration

Difficulty with account.apple.com – Privateness Consent and Account Migration

I am encountering an issue with account.apple.com when making an attempt emigrate my account to an Apple ID.

Once I click on the Proceed button to just accept Apple’s privateness phrases, I obtain a 500 Inner Server Error. Here is the request and response:

Request URL: https://appleid.apple.com/account/handle/restore
Request Technique: POST
Standing Code: 500 Inner Server Error
Request URL: https://appleid.apple.com/account/handle/restore Request Technique: POST Standing Code: 500 Inner Server Error

    {   "privacyConsentAccepted": true,   "phoneNumberVerification": {     "phoneNumber": {       "quantity": "",       "sort": "Approver",       "id": null,       "countryCode": "GB"     }   },   "completedSteps": ["phoneNumber", "phoneNumberVerification"],   "requiredSteps": ["phoneNumber", "phoneNumberVerification", "privacyConsent"],   "repairContext": {     "repairType": "restricted_account_conversion",     "repairItems": ["phoneNumber", "privacyConsent"]   } } 

It seems the Privateness Consent step will not be correctly offered within the UI, inflicting this error. Nevertheless, I can not submit on Apple’s boards as my account is caught on this migration course of.

Surroundings Particulars
Browser: Google Chrome Model 131.0.6778.205 (Official Construct) (64-bit)
Working System: Home windows 10

Suspected Trigger
I think the server could also be verifying if the machine is operating macOS 12 or later when the Settle for button is pressed. Since I am on Home windows 10, this could be contributing to the problem.

Steps I’ve Tried
Trying the method on completely different gadgets/browsers.
Guaranteeing the account migration conditions are met.
Checking the community request payload for clues.

Help Requested
If anybody might kindly:

1: Share this subject on Apple’s boards (as I can not log in to submit myself).
2: Provide steerage or a workaround to resolve the error.
Any assist could be enormously appreciated! Thanks prematurely.

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles