Apple confirms it has fixed widespread 'No Longer Shared' iOS bug

Posted:
in General Discussion edited May 2020
Apple on Tuesday said that it has fixed a widespread bug in its Family Sharing system that caused apps to fail to open.

The bug caused apps to fail to open, and prompted users to redownload them from the App Store.
The bug caused apps to fail to open, and prompted users to redownload them from the App Store.


Reports of the issue first surfaced earlier in May. The bug, which impacted a significant number of users, showed a dialog box that said "This app is no longer with you," and prompted impacted users to reinstall it from the App Store.

Over the Memorial Day weekend, Apple resolved the issue for all users, confirming in a statement to TechCrunch that it should no longer affect anyone on iOS.

Even before Apple worked to fix the bug, some users found that they could solve it by deleting and redownloading specific apps. Following first reports of the bug, Apple re-issued a large number of previously released iOS app updates in an apparent move to mitigate the flaw.

The bug impacted popular apps, such as Audible.com, Discord, Facebook, WhatsApp, and YouTube, among others.

It isn't clear what caused the bug in the first place, though it's probable that it was an app signing issue with Family Sharing that caused apps to behave like paid downloads that users lost the right to use.

Comments

  • Reply 1 of 4
    igrouchoigroucho Posts: 63member
    Funny to read this since my wife encountered this exact msg - which we didnt even knew existed - AFTER upgrading to 13.5!!! So ”fixed”? Seems not so much!
    (It was her Facebook app which I had to delete and reinstall as a fix)
  • Reply 2 of 4
    ralphieralphie Posts: 102member
    Likely something coming down the pipeline to inflict more pain on users. This was just a precursor that wasn’t tested properly. Issues like this just don’t appear without reason.
  • Reply 3 of 4
    fastasleepfastasleep Posts: 6,408member
    igroucho said:
    Funny to read this since my wife encountered this exact msg - which we didnt even knew existed - AFTER upgrading to 13.5!!! So ”fixed”? Seems not so much!
    (It was her Facebook app which I had to delete and reinstall as a fix)
    Sounds like you didn't "read this" — the fix had nothing to do with iOS 13.5 and was done over the weekend.
    watto_cobra
  • Reply 4 of 4
    fastasleepfastasleep Posts: 6,408member

    ralphie said:
    Likely something coming down the pipeline to inflict more pain on users. This was just a precursor that wasn’t tested properly. Issues like this just don’t appear without reason.
    Any evidence to support this? (Spoiler: No)
    watto_cobraRayz2016
Sign In or Register to comment.