Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple how is this possible. A beta product that had a software issue? /s.

Yep, I never understood the carping about beta software. Any sane individual would never, ever install a beta on their primary machine anyway, let alone start blathering on about bugs. Betas are supposed to have bugs. That’s why they are called betas.
[automerge]1570825087[/automerge]
By the way, just to pick a nit, the article talks about iOS 13.2 beta 2. Shouldn’t it be ipadOS 13.2 beta 2?
 
  • Like
Reactions: jinnj and chaicka
Yep, I never understood the carping about beta software. Any sane individual would never, ever install a beta on their primary machine anyway, let alone start blathering on about bugs. Betas are supposed to have bugs. That’s why they are called betas.
[automerge]1570825087[/automerge]
By the way, just to pick a nit, the article talks about iOS 13.2 beta 2. Shouldn’t it be ipadOS 13.2 beta 2?

yes, the screen shot in the article shows iPadOS
 
Just had this conversation this morning with @I7guy People who don't have a high tolerance for potentially buggy software shouldn't do betas. I don't, so I don't. For those who do... thank you for your service.
I have a high tolerance for buggy software. It happens. Remember the iOS 8 brick? That wasn’t even beta, or so people said.
 
When it comes to betas, install at your own risk. Especially if there’s no public beta yet.
How is this possible? It's a developer beta. It's not wonderful that some are having difficulty with this, obviously. But it's a developer beta and cannot be held to the same standards as a public beta release. I'm sure they will have a remedy in place soon™.
Im getting really annoyed by people who write stuff just in order to write something, but it doesn’t have any value. The public beta was released after multiple users, including me, reported that there is an issue. Better get informed next time before writing something cuz it’s pathetic.
 
  • Like
Reactions: canesalato
Not sure if its been mentioned yet, but I had an issue with my 12.9 iPad Pro as well on this install. It got stuck at Apple logo with status bar at full and just stuck there. I left it for a good 45 mins before finally doing a forced restart. Volume up, volume down, hold power/sleep. When I did this went back to long apple logo and status bar install again... but this 2nd time it completed without issue and all is well. Thank the maker.
 
Whoa. I am currently running iPad iOS 13.1.2 and there were some minor bugs. Like some recently opened apps on the menu bar don’t reopen the app when you click on them. Instead I have to click on the actual app on the screen. Glad i didn’t update to 13.2 cause a bricked ipad is a lot worse! Besides the one glitch i mentioned in 13.1.2 so far I am digging the new iPad iOS. But I will wait to update again.
 
Can we not use the term "Bricking" when the device can be made to work again via a restore.

Bricking means... the device is now equal to a brick. A heavy useless thing. If it can be made to work again ... it is not a brick.

Why deprive them of using cool sounding cliches like bricked, price point, and form factor?
 
As of yesterday, my iPad Pro 11" (2018) was stuck in the Install stage with the same unable to verify error message. My iPad Pro 9.7" updated fine. This morning, my iPad Pro 11" (2018) spots a new download. Fingers-cross it installs fine after download completes.
 
Apple how is this possible. A beta product that had a software issue? /s.
Such a misguided and cynical comment. There are two beta channels for iOS: a private developer beta channel, and a public beta channel. In theory, releases should be delayed between the two, in order to have developers (more experienced and usually testing from work devices) experience unexpected severe bugs, while users (through Apple!) use this time delay as a safety buffer. However, for iOS13, Apple has, for the first time, released betas with KNOWN and already reported critical flaws (including severe data loss), into the PUBLIC beta channel. This is not normal and should not be acceptable, especially as part of a stability release such as iOS13.2. It is clear that iOS13 is still in a highly unstable condition. Therefore, releasing a (flawed) beta version at the same time for the private and public beta channel is an inconsiderate move. Yet Apple keeps doing it. Please, enjoy looking down on people having trouble with their devices, if it pleases you, but perhaps keep /s for yourself.
 
Last edited:
  • Like
Reactions: gank41 and IG88
LOL that's why I wouldn't touch any iOS beta testing. As enticing as it may, having a first taste of new features and everthing, it's still a prototype with a few deadly bugs to be expected. Yes most of the time iOS beta should be fine, but this is one of those rare, special cases.

You've been warned. It's a beta, it may be 20% or 90% usable, I still wouldn't use it because all my Apple hardware is essential to me. Of course I have a few old Apple stuff in my drawer, but they're too old for this.
 
Last edited:
Such a misguided and cynical comment. There are two beta channels for iOS: a private developer beta channel, and a public beta channel. In theory, releases should be delayed between the two, in order to have developers (more experienced and usually testing from work devices) experience unexpected severe bugs, while users (through Apple!) use this time delay as a safety buffer. However, for iOS13, Apple has, for the first time, released betas with KNOWN and already reported critical flaws (including severe data loss), into the PUBLIC beta channel. This is not normal and should not be acceptable, especially as part of a stability release such as iOS13.2. It is clear that iOS13 is still in a highly unstable condition. Therefore, releasing a (flawed) beta version at the same time for the private and public beta channel is an inconsiderate move. Yet Apple keeps doing it. Please, enjoy looking down on people having trouble with their devices, if it pleases you, but perhaps keep /s for yourself.
I don't think you could be more wrong with your opinion. The word "beta" says it all to me, which is why the "/s". If one doesn't want to risk their operational device and heed Apple's more than in your face warning when one installs beta software...that is up to the risk tolerance of the individual.

However, like other things in life, there are varied opinions, which is why I believe my comment was neither misguided or cynical. YMMV.
 
  • Like
Reactions: jinnj
To all of the people surprised that beta software is buggy: do y'all file bug reports through the feedback apps like good kids? Or do y'all just complain into the void and hope Apple will read your random forum posts? 🧐😒
 
Had this issue too, luckily I took it to an authorized place and it was quickly fixed and restored. First time I’ve really seen such a loss, couldn’t even flash it or get it to go to reset mode.
 
Anyone on iPadOS 13.2 that can tell me if you csn CMD-Space in an app, search for another app and drag it to multitask next to the app you're in (without tapping Cancel in the search field)? This feature was in iOS 12 and I miss it so much. Will Apple ever fix it??
 
My 11” Pro is actually bricked. Can’t install or do anything with iTunes. iPad likes to play games with me and disconnect during the extraction process. I’ve tried 2 different cables, formatted computer and reinstalled windows, redownloaded iTunes and the .ipsw 3 times. Tried 2 different computers. Nothing works. Going to the Apple Store today and it’s likely going to be replaced.
 
NEWS FLASH!! It's early Saturday morning in the Eastern time zone. iPad OS 13.2 Public Beta 2 was available for download on my first generation 12.9" iPad Pro. It downloaded. It installed. No bricks to be found in my house.

Move along, there's nothing to see here!

But as to the linguistic debate...

"Bricked" is a powerful cool word, and people love to use powerful cool words (especially in ALL CAPS in Twitter feeds). Since language is forever in flux, yesterday's meaning is not necessarily going to be today's. So "bricked" no longer means, "A heaping pile of melted silicon that can't even be used for parts." Now it means, "Temporarily out of service."

It's little different than the shift in meaning for "literally," which now means its former opposite, "figuratively." You may as well say, "It literally bricked my iPad," which in newspeak means, "figuratively bricked."

White is black and black is white, which considering I'm currently in Dark Mode is pretty close to the truth anyway.

And of course, "Beta" now means, "flawless." In the good old days, before my joints went arthritic, there was the internal Alpha test behind the corporate firewall - maybe hundreds or a few thousand test users. Beta went to a wider group beyond the firewall, in order to expose the not-yet-perfected software to a wider range of hardware/software configurations (and monkeys with typewriters). Finally came the Public Release, which was always criticized as having been released prematurely as it was still imperfect. Now it seems "Beta" means "Public Release, practically perfect in every way," so all debugging is on the shoulders of the Alphas (male, female, or neutered).

Oh, if only the first public release was perfect... I'd love to see all those "I'll never install a dot-oh" perfectionists wait years for something other than a dot-oh to come along.
 
Hard brick in 2019... that's bad... :rolleyes:
Well, seems to affect OTA updates only (?). I always flash the full image via iTunes... not a fan of incremental updating.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.