Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Meh. So far I’m very happy with the stability and battery life of the first RC on my 13 Pro, I think I’ll miss this one and just wait for the public release.
I thought for a moment you were serious...:(

I just saw all the laughing faces in your post.. i was even planning to update to 18.2 this week....
 
The first RC1 caused many of my apps to quit immediately upon launch (slide down to the home screen). I had to reinstall these apps as a workaround. Maybe RC2 would prevent this critical bug.
Microsoft SwiftKey crashes on RC1 every time I try to create a new theme (from my own photo background).

If this delta update is small, I don't see the harm in installing it.
 
  • Like
Reactions: Macaholic868
I upgraded from iOS 18.1.1 to 18.2 RC2 (less than an hour ago) on an iPhone 11 Pro and, at least in the first few minutes of testing, it seems to work fine for a phone that's 5 years old. It's smooth, doesn't lag, opens all the apps I had on 18.1.1 and I haven't found any bugs yet. Obviously, I didn't expect big changes compared to 18.1.1 since the IA in its various features is not possible on the iPhone 11 Pro. I haven't tried 18.2. RC1, so I can't report any differences or improvements compared to RC2. Probably, this RC2 will be very similar (or equal) to the public release. I'll check if, when the public release comes out, the build will be 22C151 or later changes. Now, I have the message under battery "the update is finishing in background": certainly, the performance will be more real when it finishes. As usual, the background update and indexing will last a few hours or a day/two.
 
RC1 to RC2 is only ~294 MB on my 15 Pro.
Size doesn't actually mean anything for these updates and is not indicative of what was changed. Software is released in library modules. Say there's a library that contains all the API's for audio functions and another library for networking functions. Apple could change one line of code in each and the update would require including both modules in their entirety. Or they could completely rewrite those modules and the update could have similar size to the one line update. Size just tells us where the changes happened and not so much how many changes were made. Comparing the size of the new library versus the prior library could tell us if changes were minor or not. Depending on what was changed, the new library could be smaller or larger than the old one.

What this means is that the libraries changed added up to about 294MB in size, not that they made 294MB worth of changes. Hope that makes sense.
 
Thought Dec 9 is the release date of 18.2. Didn’t macrumor hint for that?

Probably a critical bug qualified another RC. Wish not to wait so long for the formal release of 18.2
 
Last edited:
  • Haha
Reactions: frenchcamp49er
Oh so yet another week of iPhone commercials advertising “with Apple intelligence” that isn’t available 😆
Not necessarily. I've seen Apple release an RC2 and then the public final release the next day. It's likely they found a high priority bug or two and wanted to slip them in. They've had a week's testing on RC1 and it's possible the changes to RC2 are minor and therefore don't need a whole week, probably just enough time to make sure they work right.
 
I have a coworker whose favorite animals are unicorns and sharks, so I wonder what the Genmoji would look like with a prompt of "Unicorn with sharks for arms"?
Here's a meta AI response from WhatsApp.
 

Attachments

  • IMG-20241209-WA0000.jpg
    IMG-20241209-WA0000.jpg
    139.4 KB · Views: 65
Thought Dec 9 is the release date of 18.2. Didn’t macrumor hinted for that?

Probably a critical bug qualified another RC. Wish not to wait so long for the formal release of 18.2
The Darwin Kernel (dec 5th build) is way newer then beta 4 and first RC that used a Darwin Kernel (Nov 15th both). Likely another zero day fix across all the OS's that uses that Darwin Kernel. Possibly something was also fixed but its takes something particular important with a RC2 across multiple OS's.
 
On my iPhone 16 Pro Max it was 469.8mb.

Hoping this is the actual release version, and they did not mess with anything that makes the battery life worse. RC1 was the best battery life I was getting on the beta's, which I have been running since I got my launch day iPhone 16 Pro Max!

:apple:
 
On my iPhone 16 Pro Max it was 469.8mb.

Hoping this is the actual release version, and they did not mess with anything that makes the battery life worse. RC1 was the best battery life I was getting on the beta's, which I have been running since I got my launch day iPhone 16 Pro Max!

:apple:

All they would’ve done is fixed one or more bugs that they felt it necessary to fix prior to the actual release. If RC 2 does the trick it’ll be the same build that becomes the public iOS 18.2 release so I don’t see why anyone who had RC 1 already installed or anyone who wants iOS 18.2 before the public release day wouldn’t upgrade to it now.
 
  • Like
Reactions: Realityck
I have a coworker whose favorite animals are unicorns and sharks, so I wonder what the Genmoji would look like with a prompt of "Unicorn with sharks for arms"?
I just got a unicorn underwater with sharks in the background. However, “unicorn shark” gave some interesting results, and “shark unicorn” returned basically the same.
 
Didn't encounter any issues with RC1 on my iOS devices, but my iPadOS encountered TV app crashing playing downloaded content and some degraded battery performance. I updated both devices, hopefully that resolves those issues.
 
Meh. So far I’m very happy with the stability and battery life of the first RC on my 13 Pro, I think I’ll miss this one and just wait for the public release.
They only release an updated RC if there is a major bug. Most likely this is the final release unless another major bug is found.
 
iOS 18.2 (22C151) still has a long-standing Mail.app bug where if you Reply to the last message in a thread wherein you had sent the last message, the new reply message incorrectly sets the To: to your email address (the From: from that last email), rather than the other recipients in the thread (the To: in the prior message).
Expected behavior should be for the Reply to a message YOU sent NOT to be addressed to you but to the other recipients.

And yes, THAT IS the 'expected behavior', that's the way it has worked on Mac OS for years and how it works on iPadOS 18 (although it was also broken there for a while, starting a few years back, but was fixed). Curious that it works on macOS and iPadOS, but not iOS… guess no one at Apple does much emailing from their iPhones.
 
is photos put back to ios 17 version?

to me it looks like version 18.1.1. What do you mean specifically? If you mean the bottom menu we had on iOS 17, it has not returned and is similar to the one in 18.1.1.

Aside from that, on my "modest" 11 Pro it works very smoothly, for now..
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.