christo747
macrumors member
Hope they fix the bugs. I got a ton of problems. Wifi-problems, no sound in apps, touch not responding, lag, jiggle-mode is an absolute chaos etc.
Last edited:
Apple Releases First Public Betas of iOS 14.2 and iPadOS 14.2 With New Shazam Control Center Options
- Thread starter MacRumors
- Start date
- Sort by reaction score
PBG4 Dude
macrumors 601
14.1 is probably being loaded onto the new iPads and iPhones that will be released next month. They have to be manufacturing them by now.
PBG4 Dude
macrumors 601
Oh snap! Don’t tell my iPhone 11, somehow it’s running 14.2 (18B5052h).
adrianlondon
macrumors 603
Word of warning on 14.2: The Authy app crashes after a few seconds. You can still get your auth codes but you gotta be quick 
Edit: New Authy version fixes the crash.
Edit: New Authy version fixes the crash.
Last edited:
EugW
macrumors P6
So, why aren't we getting 14.1.2 beta? Just curious. I don't recall this happening in recent times, but maybe I just missed it.
BaltimoreMediaBlog
Suspended
Did the update, but got no Shazam in the Control Center. Puzzled as to why as the app is already on my iPhone.
Apple_Robert
Contributor
Remove the profile and enter DFU mode. That will give you iOS 14.
Apple_Robert
Contributor
Rather surprised that Shazam is noteworthy to be included in Control Center. I jumped off the beta train with the purchase of my new series 6 watch. Hope Apple keeps killing the bugs.
digitalexplr
macrumors 65816
My XR is running 14.2 b1 as well. Got before it was pulled. Haven't had any issues. Battery has been excellent.
Babygotfont
Suspended
still a problem for those with 850+ apps installed ... app earch feature outside of app library doesn't work properly
there's an FB open but don't know if iapple has acknowledged the bug
there's an FB open but don't know if iapple has acknowledged the bug
atomic.flip
macrumors 6502a
What a joke! Why aren’t they supported? Let me guess... too many hardware versions and too many code bases.
Hey Apple, remember you did this to yourselves in the 90s and went bankrupt. Don’t screw up what Steve did for you!
adrianlondon
macrumors 603
Good question! I just tried it, and I had to click on the notification (which opens Shazam) then click "add to library". It wasn't automatic. Pity.
zombierunner
macrumors 68000
Are they skipping 14.1?
puckhead193
macrumors G3
did I miss apple releasing 4.1? I never update my iPhone with a brand new iOS
tha_man
macrumors regular
Thanks for answer. I sure hope they will at least add the option to do this automatically...
It wouldn't really work like that in relation to that, it would still then just be 14.1. In this case it's more related to 14.1 likely being tied to new phones that will be coming out, so the development on anything beyond what's already set to go onto the new phones continues in 14.2 which would be an update to both current and new phones once it comes out.
Seems like something likely had to be updated or tweaked for those that was important enough for one reason or another that the update got pulled and would become available at some point once what needed to be tweaked or added has been done, perhaps even simply just with the next beta update.
atomic.flip
macrumors 6502a
Sure what you’re saying makes sense and is plausible. Unfortunately, I’ve become painfully aware of a code management issue that Apple has yet to address during their development process.
Basically code is checked out and worked on. Often by multiple engineers each working on different portions of code. (Usually different components entirely.) Then when they’ve made their changes they check the code back in and periodically a full build is tossed out to the masses as either developer or public beta.
The issue that appears to happen is new code often gets overwritten with old code during the checkin process. It becomes a huge mess when you have several engineers working on different components. They seem to do some patch fixing by the end of the process but the process is unnecessarily painful for both third party developers and beta testers since things that should not break during development often do. And it’s not an excuse to say it’s beta. It’s fine to fix bugs and fine to develop new functionality and have that functionality be buggy during the process. But breaking existing functions that have little to nothing to do with what you’re working on is just plain sloppy.
This is a problem that just becomes more compounded with the more device variants they develop for. At one time we had one code base. One iPhone.
Robert.Walter
macrumors 68040
“The new iOS 14.2 beta will likely be in testing for some time as Apple works on releasing new iPhones, with the new iPhones expected to debut sometime in October.”
Why should this be the case? It’s not like the folks rolling out the new phones are writing and debugging software.
I would think the s/w folks would be going all out to have this or the following update ready for the roll out.
Why should this be the case? It’s not like the folks rolling out the new phones are writing and debugging software.
I would think the s/w folks would be going all out to have this or the following update ready for the roll out.
Babygotfont
Suspended
the programming monkeys at the corporate spaceship have run amuck
At one time an abacus was also the height of technology. In some ways it's just the nature of the beast, so to say. That said, that doesn't mean that doing things in better ways isn't something to strive for and actually actively work on.
They likely will be doing that going through the beta phases and all that so that it would be all set to go once it's ready. In the meantime there will likely be some 14.0.x releases to address various bugs or other issues that are currently there.