XPost: misc.phone.mobile.iphone   
   From: ithinkiam@gmail.com   
      
   Maria Sophia  wrote:   
   > Chris wrote:   
   >> Maria Sophia  wrote:   
   >>> Hi Chris,   
   >>>   
   >>> Thanks for the reply as the topic here is how iOS really works, when, we   
   >>> all are now aware that no other common consumer OS works this way at all.   
   >>>   
   >>> To flesh out how iOS really works, I will respond to your points factually   
   >>> and precisely.   
   >>>   
   >>> Note this is the beginning of the activation-lock cascade only Apple does:   
   >>> Jan 7/8 2026    
   >>>   
   >>> And note, only Apple 'bricks' the device (over time) if you refuse to   
   >>> re-enter passwords for accounts that you never logged out of.   
   >>>    
   >>>   
   >>> Note: Apple will unlock the 'bricked' device   
   >>   
   >> It's not bricked then, is it? It's simply locked.   
   >>> but I had to manually visit   
   >>> the Apple Store and present government ID to prove to Apple who I am.   
   >>   
   >> Kinda defeats your attempts at not giving Apple your details. Doesn't it?   
   >>   
   >>>> This is 100% a you problem. You choose to do that and thus get the   
   >>>> repercussions. You claim you're logged in, but if you don't authenticate,   
   >>>> you're not.   
   >>>   
   >>> This is mixing two different concepts.   
   >>   
   >> Not at all. This is still 100% down to your behaviour.   
   >   
   > This thread is about how it works.   
      
   Nope. This is simply an exercise in extreme behaviour and not within design   
   parameters.   
      
   > 4. Apple documents the existence of these tokens in its developer   
   > documentation.   
      
   Ah! Let's see what they actually say. Shall we? I'll mark them as Success   
   or Fail in relation to supporting info on session tokens.   
      
   >    a. StoreKit transaction tokens   
   >          
      
   API docs on App Store transaction management. No mention of tokens nor   
   sessions nor timeouts. [Fail]   
      
   >    b. App Store Server API signed transaction tokens   
   >          
      
   Related to the above for a specific object. No mention of tokens nor   
   sessions nor timeouts. [Fail]   
      
   >    c. Renewal info tokens   
   >          
      
   404 [Fail]   
      
   A search of the API shows no endpoint matching that name.   
      
   >   
   >    d. Apple ID authentication tokens   
   >          
      
   404 [Fail]   
      
   >    e. Apple documents that App Store sign in is separate from iCloud   
   >          
      
   That is not at all what that link explains. It's for people who want to   
   change the country of their residence to access local Apple services and   
   apps. [Fail]   
      
   Five attempts and five fails. Impressively bad.   
      
   If I had to guess you got chatgpt to provide you the "documentation" which   
   doesn't exist so it made it up. Not the first time you've reported chatgpt   
   answers as fact without checking them.   
      
   > These links show that iOS uses multiple authentication tokens with   
   > independent expiry and that App Store authentication is separate from   
   > iCloud authentication.   
      
   Not at all. Not even close.   
      
   If you still believe those links are accurate, provide the explicit quote   
   which supports your assertion that each Apple service uses different tokens   
   and they timeout differently.   
      
   > The behavior observed during testing matches Apple's documentation.   
      
   It doesn't match any document you've shared.   
      
   The behaviour you're demonstrating is such an extreme edge case that I   
   doubt there is *any* documentation covering it. No developer will be   
   prepared for a genuine user to continually ignore requests to access Apple   
   services on an Apple device for years on end.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)