App: MobileMeDelegateError after 2FA #221

Activity

1. alixti

   added

   bugSomething isn't workingSomething isn't working

   @appIssues regarding the OpenTagViewer Android appIssues regarding the OpenTagViewer Android app

   on Sep 16, 2026
2. parawanderer

   self-assigned this

   on Sep 16, 2026
3. parawanderer commented on Sep 16, 2026

   

   parawanderer

   on Sep 16, 2026

   Owner

   More actions

   Your screenshot has the answer in it, and it is not terms of service — the app was wrong to say so. Sorry for sending you to check iCloud.com.

   What Apple actually returned: status=1, status-message='A server problem is blocking Apple ID sign in. Try signing in later.', and no localizedError field at all. That last part is the tell: localizedError is the channel unaccepted terms arrive on, and it was empty. Your password and your verification code were both accepted, so signing in itself worked. What failed is the step straight after, where Apple decides whether to open iCloud for the account.

   What it probably is. I want to be clear that this is inference, not something I can prove — I cannot reproduce it without a throwaway Apple ID, and Apple documents none of this. But every project that signs in the way this one does runs into the same delegate status, and always on the same kind of account. I searched for the exact string in your screenshot and found it in Macless Haystack:

   • dchristl/macless-haystack#84 — the identical response, logged in full: {'delegates': {'com.apple.mobileme': {'status': 1, 'status-message': 'A server problem is blocking Apple ID sign in.'}}}
   • dchristl/macless-haystack#86 — the same status: 1 with Account limit reached instead, from someone who says they had created a new Apple ID without owning an Apple device
   • dchristl/macless-haystack#87 — the same thing, where the tooling tells the user: "It seems your account score isn't high enough. Log in to https://appleid.apple.com/ and add your credit card (nothing will be charged) or additional data to increase it."

   That last line is that project's message rather than Apple's, so treat it as their read of the situation and not as an official explanation. The common thread across all three is a fresh Apple ID that has never been used on real Apple hardware, and you said this was "another account separated from my main account", which fits.

   So the thing to try: sign in at https://appleid.apple.com with that account, fill in the account details — a payment method is the one people specifically name, and nothing gets charged — and then try the app again. Note that Apple's own "Try signing in later" appears to be misleading here: in those threads it does not clear on its own. If you have a main account that already works, that is the faster route.

   Two changes came out of your report, though neither of them fixes your account — they are about the app not misleading the next person:

   • The app will no longer call this a terms problem. It gets its own message saying sign-in worked, that terms are not the cause, and pointing at the above. (Tell iCloud being refused apart from terms of service #223)
   • FindMy.py stopped advising the terms flow when the response never used that channel. (parawanderer/FindMy.py#5)

   If appleid.apple.com does clear it for you, please say so here. That would turn a guess that several projects share into something actually known, and there is nowhere else it is written down.

   Drafted by Claude Code, reviewed by @parawanderer
4. parawanderer

   closed this as completedin #223on Sep 16, 2026