On iPad or iPhone? I have it randomly on the iPad, the first one worked , the second didn’t, third worked.
Update: so far the first photo which got the error keeps being impossible to mark up. But only that one.
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases iPadOS and iOS 14.1 With Multiple Bug Fixes Ahead of iPhone 12 Launch
- Thread starter MacRumors
- Start date
- Sort by reaction score
Update: so far the first photo which got the error keeps being impossible to mark up. But only that one.
Made the upgrade from 13.7 to 14.1 tonight. Used iTunes to download and install the full IPSW installation file. After the installation finshed backing up the phone, I ran into the dreaded (and apparently common for iOS 14) Error 4000. Restarting both the device and the PC a couple of times didn't help.
Lot of solutions out there on Google trying to convince you that it's an iTunes registry issue and that you need to buy an application to fix it. But, the solution that worked for me (and apparently a lot of others who run into this issue) was to disable the iPhone passcode. Once the installation finished, the welcome screen prompted me to create a passcode. Disabling the passcode requires resetting Apple Pay, but Touch ID still works fine.
So far, I haven't really noticed huge differences in the overall experience. And my battery is still at 99% after running 15 minutes unplugged. Might have helped that I kept the phone plugged into my PC for the first half hour after upgrading. it felt hot right after installation. But, right now it feels cool.
I really don't get all the uproar over the application library, whether it's the jaded reviews that fawn over it or the people on this forum who complain about it. It's stuck way at the end of all my application screens, and I have my screens arranged such that my least frequently used apps are at the end. The big benefit that i potentially see with the app library is that I can remove the less frequently used apps from my screens without having to stash them inside folders, and just keep them in the app library. Otherwise, I don't get why people get all bothered by it one way or the other.
My main concern has been the cell reception, which went awry on my phone with iOS 13.7. In some areas, I see bars for LTE service, but I'll get speeds so low that they're unusable (>0.1 mbps). Sometimes, restarting the phone or switching the LTE service off (and relying on the HSPA+/4G network) helped. But, other times, the LTE service was useless.
Lot of solutions out there on Google trying to convince you that it's an iTunes registry issue and that you need to buy an application to fix it. But, the solution that worked for me (and apparently a lot of others who run into this issue) was to disable the iPhone passcode. Once the installation finished, the welcome screen prompted me to create a passcode. Disabling the passcode requires resetting Apple Pay, but Touch ID still works fine.
So far, I haven't really noticed huge differences in the overall experience. And my battery is still at 99% after running 15 minutes unplugged. Might have helped that I kept the phone plugged into my PC for the first half hour after upgrading. it felt hot right after installation. But, right now it feels cool.
I really don't get all the uproar over the application library, whether it's the jaded reviews that fawn over it or the people on this forum who complain about it. It's stuck way at the end of all my application screens, and I have my screens arranged such that my least frequently used apps are at the end. The big benefit that i potentially see with the app library is that I can remove the less frequently used apps from my screens without having to stash them inside folders, and just keep them in the app library. Otherwise, I don't get why people get all bothered by it one way or the other.
My main concern has been the cell reception, which went awry on my phone with iOS 13.7. In some areas, I see bars for LTE service, but I'll get speeds so low that they're unusable (>0.1 mbps). Sometimes, restarting the phone or switching the LTE service off (and relying on the HSPA+/4G network) helped. But, other times, the LTE service was useless.
Yeah it does seem to be very random. I had no issues after updating my iPhone 11 / Watch series 5 to iOS14 / watchOS 7 but my wife did see the issue after updating her iPhoneXR / Watch series 5.
Unpairing / Re-pairing the watch does seem to be a pretty reliable fix for the issue should you encounter it.
Just tried it on my 1st Gen 2015 iPad Pro a few times, no problems with mark up also. Only issue I'm seeing on the iPad is another battery hit. I know it's a 5 year old device...I've noticed this battery drain for a while though.
Mark up on my XS Max still works fine.
No odd activity overnight for iPhone or iPad with apps running in background - like personally back in July (I had Dropbox, others had Apple Music constantly going and draining battery)
So far so good, I'll see how this runs on a full day with the new 14 ios.
No keyboard lag at all on my end, tried multiple messages, emails..Both iPhone and iPad 1st gen Pro.
This was one (of quite a few bugs) I saw here that made me hold off until yesterday to upgrade from 13.7 to 14.1. SO FAR....I'm not seeing any problems on my XS Max.
The error 4000 is easy solvable logging out and back in from your iTunes account and it happened to me as well from 13.7 to 14. I know you already fixed it in another way but this method it’s easier I think.
No idea what there being public betas has to do with anything, other than that it widens the pool of Stupid. I reiterate, don't run beta software on production devices.
Ugh. Did the minor update from 14.x.x to 14.1 and the iCloud backup now says I don't have enough space in my 200 GB plan. Seems it has decided it wants to duplicate my photo library. Had my 120 GB of photos backed up, now it wants to add another 120. Don't want to spend time trying to deal with it, so just paying the extra bucks for 2 TB plan. Apple is doing a good job getting a few extra bucks out of me.
Huh. I haven't seen that behavior in any of the iOS 13 updates, is that a new thing for iOS 14? Of course I disable as much of Siri as reasonable in any case, so maybe I've hit on whatever switch it is.
I got tired of running into that message of getting low on iCloud storage so I just said screw it and figured I will just back up my photos to another service or my computer...Ugh. Did the minor update from 14.x.x to 14.1 and the iCloud backup now says I don't have enough space in my 200 GB plan. Seems it has decided it wants to duplicate my photo library. Had my 120 GB of photos backed up, now it wants to add another 120. Don't want to spend time trying to deal with it, so just paying the extra bucks for 2 TB plan. Apple is doing a good job getting a few extra bucks out of me.
You may already know, but yes it has finally been fixed.
LOL at all the people who down voted you and me though. The Apple faithful, couldn’t find less demanding customers.
I installed the 14.1 update last night, went out for a run today and it tracked properly; heart rate, map etc... Definitely no reset, I'm not getting into all that as last time I did that I lost all my health data. Hope I'm not giving you false hope, what's not working for you?
No they didn't. I used to have all-day long battery life on iPhone X using iOS 13. Now it's gone on iOS 14. I have to put my phone on charger at 19:00. I'm very disappointed with that behaviour, beacause I believe that there is nothing wrong with my battery or my phone. Just Apple needs push me to buying new iPhone. Sad.
I tried to update an XS running 14.0.1 from a new iMac running 10.15.7. Said the download was corrupted. Tried again. Same result. Knowing the clinical definition of insanity, I tried over WiFi (much smaller download). No problems.
Same download issue for an iPad Pro running iPadOS 14.0.1, are result when updating over WiFi.
Separate issue with automatic backup/sync to the Mac before attempting the downloads: got a generic "can't sync" message. Researched online; almost all the results were about what to do in ancient versions and reference something called iTunes. (I jest, but they did.) Checked Apple's support site: lots of voodoo suggestions, but nothing that sounded plausible. Since the Mac is new, I figured, why not try hitting that "Change Password..." button under Backups in the Finder window (when an iThing is attached). iCloud remembered my old password, I entered and verified a new and better one, and Bob was my proverbial uncle. Is the system ID or something else in hard/firmware involved? Or is it that I now have a shiny, new machine with a T2 chip (caution: monitor all domestic help)?
Anyway, Apple, if you read these fora, that's three (3) things that did not Just Work™.
Same download issue for an iPad Pro running iPadOS 14.0.1, are result when updating over WiFi.
Separate issue with automatic backup/sync to the Mac before attempting the downloads: got a generic "can't sync" message. Researched online; almost all the results were about what to do in ancient versions and reference something called iTunes. (I jest, but they did.) Checked Apple's support site: lots of voodoo suggestions, but nothing that sounded plausible. Since the Mac is new, I figured, why not try hitting that "Change Password..." button under Backups in the Finder window (when an iThing is attached). iCloud remembered my old password, I entered and verified a new and better one, and Bob was my proverbial uncle. Is the system ID or something else in hard/firmware involved? Or is it that I now have a shiny, new machine with a T2 chip (caution: monitor all domestic help)?
Anyway, Apple, if you read these fora, that's three (3) things that did not Just Work™.
I was going to try that next if I hadn't found the solution to disable the passcode. The only question would be whether I need to log out of the iTunes account on both my phone and on my computer. For the phone that would not be an issue, since I used to do that regularly (and restart) to free up storage space.
But, on my PC, logging out of iTunes has created issues before, with the application not always properly connecting to files that I had created and stored locally (I have lossless files and uncompressed LP transfers). So, I would have to delete those albums from iTunes and then re-add them to the library.
Last edited:
So, If I were to upgrade my 7 Plus to either an 11 line, or 12 line of iPhone, would i trade stability for instability ? Just wondering if newer devices are prone to more bugs than older devices? The only problem I've had with mu current iphone and ipad were the initial releases of 13. The other thing is, I'm willing to try FaceID, but if I don't like it, could i disable it and just stick with a Passcode, since the new devices don't currently have TouchID? My other option would be to switch to Android as there are devices that have both technologies. I want to give Apple a fair chance though because their new phones look nice. I just don't know if the new apple is for me anymore. I am someone who has grown up with Apple since the 80's and more and more the direction they're going is making other options start to look better for my way of doing things.
What I meant it's logging out of your iTunes account, on your computer not on any device, brr, I know it's a pain in the neck there.
I 'm still on Mojave and it works on Catalina too, but you need to have iTunes 12.9 or and 12.6.5.3
I'm running iTunes 12.10.9 on Windows 7. I know my setup is on borrowed time, since Apple will likely cutoff support for Windows 7 soon (I mean, even Microsoft cut off mainstream support for Windows 7 earlier this year). Originally, when I saw the error I thought that Apple was screwing around again with an orphaned version of iTunes, and I went to the download site to verify that I was running the most current version (not just the latest version that Windows 7 can run). I remember when an orphaned version of iTunes on my iMac allowed me to update iOS, but then iTunes could no longer read or backup the device once the update finished. Fortunately, I was still within the code signing window for the older iOS version and I promptly downgraded.