iPadOS 17.7.7 update has really caused issues to my iPad Pro

New security update 17.7.8 out today fixes this problem.

Update: it is necessary to turn off all automatic update features on the iPad before reverting to 17.7.6. Then the forced update to 17.7.7 does not occur. I forgot I had Security Responses & System Files set to automatic in my first attempt.

hendrix1975 wrote:

I submitted a Bug Report via Apple's Product Feedback portal. I had to select 17.7.6 as the OS, 17.7.7 isn't on the dropdown menu.

That is because iOS 17.7.7 is no longer available after Apple has pulled the update. They are aware of the problems with this version, thanks to the feedback they have previously received, and you can expect an update/fix. There has been no time frame publicly stated, so you will just have to wait for the fix to come.

So ios version 17.7.8 is out. I installed it a few minutes ago on my 6th gen ipad and I'm cautiously optimistic about it so far. Some apps that were logged out are logged in again, YouTube stopped crashing and logging out though I did reinstall it once I updated the ipad just in case. Some apps also remember user settings after opening and closing. I do need more time with it before saying it was fixed.

Just installed 17.7.8 and seems to solve all my 17.7.7 issues :-)

THANKS APPLE ;-)

Installed the 17.7.8 update and all seems ok so far. Fingers crossed!

I must confess I dreaded this would take much, much longer.

lro_ wrote:

• I rolled back to 17.7.6:

I lost my apps because my only cloud backup was created on 17.7.7

• however, all other data (iMessages, Photos, etc...) synced correctly from the cloud

• bug has disappeared

• interestingly, the 17.7.7 update is longer available...

iPadOS 17.7.7 has a number of significant issues - many of which you will find described within recent threads in this Support Community.

Apple has withdrawn the iPadOS 17.7.7 update pending release of a fix. While Apple has not issued a timescale, you might reasonably anticipate that a revised update will be released sooner rather than later.

egg122 wrote:

Do you have any idea how to get Apples focus on our problems?

There's focus...

iPadOS 17.7.8 has been released - and is now available for download.

Release 17.7.8 seams to solve the issues I had.

Try it and tell us.

Just downloaded 17.7.8, which seems to have fixed most of the bugs introduced with 17.7.7 :)

For me, these residuals remain:

Klassiki and Arrow Player (which clearly use the same engine) now won’t let me login at all, and don’t download at all after deleting the Apps

U / UKTV Play cannot connect to its server

Onecta - which was fine on both 17.7.6 AND 17.7.7 now won’t let me login

So… looks like some 3rd party mopping up still to complete?

hendrix1975 wrote:

Updated my iPad to 17.7.8 and it’s back to normal. Thanks for the quick turnaround, Apple team!

So far, good news for all that have installed the iPadOS 17.7.8 [fixed] update..

nafrye wrote:

I have the same iPad Pro. All apps that are not Apple apps want me to log-in before the app will open. Some apps refuse to update even when you click on the word “update”.

You are a little late to the party. Update your iPad to 17.7.8.

Problem solved! You may have noticed that Apple resolved this problem very quickly and many are thankful for that.

Ios 17.7.8 fixed most problems with apps not retaining settings etc, but in the case with Youtube this only lasted for a period (maybe 30 days or so), and then summarily went back to not saving settings/history at all in this app. There has been at least 2 updates to Youtube app since then but still no change.(IPad 10.5”)

Cyberneticist wrote:

That may be the case, but I would also add that first party apps (Weather, Pages, Numbers, Keynote) are also affected, and currently Notes isn't syncing between devices if you create or edit the note on the affected iPad, so if it is the case, it seems internal apple dev teams are also not performing best practice!

I think the problem is that there are many different problems being reported that are unrelated. Early on the problem was being characterized as saying iCloud now only supports iOS 18. Other issues were reported of not being able to use full screen when using a particular app. Then it progressed to being a sign in problem with banking apps and also with the Favorites bar disappearing.

In no way do I think that the use of NSUserDefaults is the cause to all the problems seen here, but for the case reported of sign in problems when the user id is stored in a UserDefault, then I could absolutely see where that could be the cause and that was also to a response to a developer that reported that the results were now nil. Apple specifically told Developers to not do that and refused to approve apps a year ago if they did not provide a reason for the use of UserDefaults.

For your issue of Notes not syncing after the update, then that is an issue that needs addressed and would continue to work with Apple Support directly yourself, instead of relying on what other users report from their communication with Apple. When you do this, I would recommend to stick with the first party app issues to avoid your concerns being dismissed as a third party issue where it is the Developers responsibility to test their apps with the pre-release iOS versions to give them time to update their apps.

Contact Apple Support - Apple Support

Mac Jim ID wrote:

Developers have been warned for over a year that they must include the reasons for using NSUserDefaults as it could be used as a fingerprinting measure to identify the device or user. Login details should not be included in the NSUserDefaults and for those that are having to re-enter their login, that is most likely the cause. I cannot confirm this is the reason, but based on what this developer has found out, it appears they have ignored these warnings or there may be others as well.

I doubt this is an issue of developers ignoring warnings, because:

1. If an app doesn't use the latest privacy requirements, it won't be approved for distribution.
2. NSUserDefaults doesn't know the purpose of the text it saves, so it can't selectively refuse to retrieve login info. Also, at least one of the apps I develop is failing to retrieve user settings that are not login-related.
3. At least two of the apps I develop declare the use of NSUserDefaults per Apple requirements and are still having this problem.

It seems like NSUserDefaults is simply broken ... but we'll have to wait and see for sure.