If you’re a developer, and you have a non-critical update pending release, I suggest waiting a few days for this to presumably get sorted out before releasing it.īecause if this happens to you, all of your most active users, the people who will install updates within hours of them becoming available, will be stopped in their tracks. Below is a growing list of affected apps. I’ve heard reports of this happening with numerous updates released on July 3rd, 4th, and 5th. The only fix for people with bad copies, once good copies are being served again by the App Store, is to delete and reinstall the app. I haven’t yet received a response from App Review, so I don’t know whether the fix was because I made noise, or simply because time passed, which may, for instance, expire a cache with the bad data. ![]() As far as I know, the problem hasn’t recurred since then. ![]() About two hours after the update went live, a correct, functional version of it started being distributed on reinstalls. I emailed App Review less than an hour after the update went live and yelled about it on Twitter. Delete and download it again from the App Store.”ĪppleFairplayTextCrypterSession::fairplayOpen() failed, error -42110
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |