Apple pulls second iOS 13.2 beta for some iPad Pro models
Apple has withdrawn the second developer build of iPadOS 13.2 from download for some models of iPad Pro, after reports surfaced where testers effectively bricked their mobile devices and needed to perform a full restore of the operating system.
Apple released the second build of iPadOS 13.2 and iOS 13.2 on Thursday to participants of its developer beta testing program. The build was also accompanied by the second beta of tvOS 13.2 and third build of watchOS 6.1.
Following the seeding of the iOS and iPadOS builds, reports from users started to appear on the Apple Developer Forum, with users being offered messages saying they were no longer connected to the Internet during the installation process, while others saw the message "Unable to Verify Update."
In some cases, users were unable to actually use the iPad Pro, prompting a hard reset, which didn't work. In such cases, a restore of the operating system to an earlier build or the public release rectified the issue.
The reports seem to indicate only the 2018 iPad Pro releases are affected by the issues. Other models of iPad Pro, iPad, and iPhones running iOS 13.2 beta 2 are seemingly unaffected. Apple has since blocked access to the build for the relevant iPad Pro models.
The second build of iOS 13.2 introduces new emoji to the mobile operating system, an option to opt-in to Siri improvements by sending audio recordings, and changes to how video settings function in the camera, among other alterations.
AppleInsider, and Apple itself, strongly recommend users don't install the betas on primary devices or hardware they deem as "mission critical" at all, as there is the highly remote possibility of data loss or other issues. Testers should instead install betas onto secondary or non-essential devices as a safer alternative, and to always make sure there are sufficient backups of important data before updating.
Apple released the second build of iPadOS 13.2 and iOS 13.2 on Thursday to participants of its developer beta testing program. The build was also accompanied by the second beta of tvOS 13.2 and third build of watchOS 6.1.
Following the seeding of the iOS and iPadOS builds, reports from users started to appear on the Apple Developer Forum, with users being offered messages saying they were no longer connected to the Internet during the installation process, while others saw the message "Unable to Verify Update."
In some cases, users were unable to actually use the iPad Pro, prompting a hard reset, which didn't work. In such cases, a restore of the operating system to an earlier build or the public release rectified the issue.
The reports seem to indicate only the 2018 iPad Pro releases are affected by the issues. Other models of iPad Pro, iPad, and iPhones running iOS 13.2 beta 2 are seemingly unaffected. Apple has since blocked access to the build for the relevant iPad Pro models.
The second build of iOS 13.2 introduces new emoji to the mobile operating system, an option to opt-in to Siri improvements by sending audio recordings, and changes to how video settings function in the camera, among other alterations.
AppleInsider, and Apple itself, strongly recommend users don't install the betas on primary devices or hardware they deem as "mission critical" at all, as there is the highly remote possibility of data loss or other issues. Testers should instead install betas onto secondary or non-essential devices as a safer alternative, and to always make sure there are sufficient backups of important data before updating.
Comments
Unfortunately, I have 13.2 on my 2018 iPad Pro which is my test development device - no problems so far, but I will say head need to roll at Apple about iOS 13's readiness for deployment. From a developer perspective there are multiple bugs - the UISearchController component, a critical feature of many apps, was rewritten and has major bugs still in formatting. The seriously need to do maintenance releases for iOS14 and iOS15 to restore confidence.
I run IpadOS 13.1.2.
Other apps ‘freeze’ frequently when in use such as : Safari, Files (iCloud), and Photos...
Apple has some fixing to do, however I cannot understand while ‘normal’ apps such as iTunes are not fully tested to handle simple tasks as playing music and scrolling in long playlists...
It just (don’t) work!
That's the whole point of a beta, and those people are test rabbits.
I'm patient, I can wait for the final release to come out. Thanks to those beta testers who are willing to test things out, but I do not feel sorry for them at all if things don't go as planned.
i regret letting my AppleTV update good thing I stopped updates on other devices.
then Microsoft came out with their service packs, and the Mac was upgraded every two years. Those things set the idea of scheduled releases. That meant that some bugs were inevitable.
with the first cellphones, there were no OS upgrades, because everything was so simple, basically just phone calls. The first generation of smartphones also had no OS upgrade schedules. I had a color Palm PDA for about three years. The OS was 3.5. Then, for $99, they came out with OS 4, which I bought for it. When I bought the Samsung i300 smartphone almost 3 years later, which was a color Palmphone with Graffiti, it had Palm OS 3.51. almost a year later I got the newer i330, because the screen was bad, and it also had 3.51. Then a couple of years later, I bought the Palm Treo 700p, and guess what? It also had 3.51! A bit later we got 3.52 and 3.53 to fix bugs. But in the three years I had that phone, it was still on 3.53. figure out how many years that OS was used. Most other were around almost as long. Nobody would stand for that today.
so, while Apple fixed that no upgrade path most had, they did cause the buggy release cycle that they and Google have. Both Apple and Microsoft have buggy computer release schedules as well. If you think it’s bad for the Mac, it’s ten times worse for Windows! I can link to articles about the Windows upgrade disaster.
so, with OSs gettin bigger and more complex, and a fixed release schedule, prepare yourselves for buggy releases. Unless companies can be convinced to relax these schedules, it just going to keep happening. A problem is that it’s been shown in studies that most people would rather have bugs than not have a continuous stream of new hardware and software features. So unless that attitude changes, bugs it is.
We are talking release software with serious obvious bugs. Someone had a go/no-go call on these releases and didn’t Hit the no go button. So not everyone but someone. Or someones. Who ever it is who made the call that made everyone’s work look bad.
They have more distinct sub OS these days they could have spaced them out to buy quality control more time more sensible pace to keep on top of these things.