Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
why would a RC2 on iOS be required?
Because there are very obvious visual flaws and features like local capture that either doesn't appear in the settings or disappears seconds after being entered.

What I don't know is whether they'll address these errors in RC2 or directly in the final version, but I think it's safer that they'll do it in RC2 because of the possibility of new bugs appearing.
 
Because there are very obvious visual flaws and features like local capture that either doesn't appear in the settings or disappears seconds after being entered.

What I don't know is whether they'll address these errors in RC2 or directly in the final version, but I think it's safer that they'll do it in RC2 because of the possibility of new bugs appearing.
I don’t think an RC2 would address any minor visual flaws. What we got in RC1 is what we are getting, the only thing that could change is if they find any critical bugs.
 
  • Like
Reactions: one more
i hope that iOS 26.2 is released at the normal release time (noon) not like 26.1 that was released at 3pm :oops:
 
I don’t think an RC2 would address any minor visual flaws. What we got in RC1 is what we are getting, the only thing that could change is if they find any critical bugs.
But I don't consider it a minor issue. The fact that in the Messages app, when returning from a message to the app's main screen, the bottom interface loads at 15fps is not a minor visual bug. It even gives the impression of a broken screen. In beta 3, it only happened in the app storage section, but in the RC it spread to the Messages app as well.

Furthermore, the disappearance of the local capture function is also not a minor bug. Apple is aware of these errors, as the reports indicate, and they will address them because I don't see them being capable of leaving parts of the system that give the impression of a broken phone or simply removing features for more than a month.
 
Unless something major under the hood is wrong, I don't see any new RC coming today on a Fri. I'm kind of feeling like the public release may be a newer build then the RC or we get a RC2 early next week before the public. But that is just my gut guessing :)
 
But I don't consider it a minor issue. The fact that in the Messages app, when returning from a message to the app's main screen, the bottom interface loads at 15fps is not a minor visual bug. It even gives the impression of a broken screen. In beta 3, it only happened in the app storage section, but in the RC it spread to the Messages app as well.

This is the very definition of a minor visual bug. Not a chance they will address this in an RC2, which usually is only there to address critical bugs. In the scale of bugs, this thing you mention is almost non-existent.

Also, how did you even notice? When I tap "back" from a message to go back to the app's main screen, the bottom interface (do you mean the text input box?) disappears in a split second. I have a hard time noticing any fps difference there at all, and I tried several times.
 
  • Like
Reactions: aperfectcircle
i updated my iPhone 14 Pro Max and boy this software is the worst ive ever used. I mean it’s so unstable and stutters, animations are not reaching peak compare to iOS 18. I’ve made the worst decision in my life. It was not worth it at all.

Reading some post here I came to the conclusion: you guys care more about what something looks than if it’s functional.

BTW: typing on keyboard feels so slow
 
RC2 is a beast on performance on my Air. But battery could be better. If you not using the phone and its sitting on wifi I get like 3 days with 50% battery left. But if I use it like "normal" I can get 4h 30 min out of it charged till 100%.
 

Attachments

  • IMG_9463.PNG
    IMG_9463.PNG
    207.1 KB · Views: 5
  • Like
Reactions: NBKindaGirl
Different Build as the RC…
Yeah even better version (hopefully)
…damn again updating 😀
 
Knowing my Luck, they'll release the same version as the RC and I'll be stuck with no CarPlay support for the next month+ due to the holidays...
 
I posted this elsewhere, but seems to make more sense here--

What I've found to happen over time is that there seems to be some kind of "A/B" testing going on.. Some of us may see some fixes in a "beta 2" release while then others seems to have things more borked at the same time. Then beta 3 comes around and folks that were borked get some fixes while the folks seeing fixes in beta 2 get more issues.. That seems to include the RC and even regular releases. It's a cat & mouse game, trying to make everyone happy.

Just like the CarPlay issues I'm having, along with a large number of others, and some folks are not seeing any of these issues at all. We'll find out soon enough I suppose.
 
Knowing my Luck, they'll release the same version as the RC and I'll be stuck with no CarPlay support for the next month+ due to the holidays...

I don’t think we’re getting the same version for public release. I have this gut feeling about a RC2 or newer public coming.
 
Guessing RC not having proper release notes was to hide the Fitness+ expansion, that or the 15th is public release date and we get RC2 today.
 
Ah so called leaker due to 9to5 Mac said:

In a sequence of posts, the account noted 23C52 and 23C54 as launch builds for iOS and iPadOS 26.2.
The RC that debuted last week also had 23C52 as its build number.

Let’s see if we will get a new build.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.