Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds Fifth Developer Betas of iOS 18.1 and iPadOS 18.1 With Apple Intelligence
- Thread starter MacRumors
- Start date
- Sort by reaction score
Try restarting your phone. That happened after updating to the 18.1 update before this one as well and a restart fixed it. The Siri glow is still the new one on mine after today's update.
Apple needs to HOLD OFF RELEASING ALL THIS UNTIL BAKED!
How cool would it have been if Apple instead did not release the iPhone 16 nor any public version of iOS18 until ALL the new features were totally up and running in a 1.0 version. Then, it would feel like going from the iPhone (1) to the iPhone 4; getting a plethora of new things and features and feel to your iPhone experience, and ...it'd be Christmas with new toys, new capabilities, new look ALL in your hands right there and then.
But instead it is the release of iOS 18 with only a couple minor new items like changing the color of icons, and in a couple months, here's some form of Apple Intelligence (beta-like), and then months later, here is this other new feature, ...drip, drip, drip.
I don't know if Steve would have done this drip-drip release ...to this extent.
The way it goes down now, it is no longer like Christmas when you get your new iPhone and new iOS.
😕
How cool would it have been if Apple instead did not release the iPhone 16 nor any public version of iOS18 until ALL the new features were totally up and running in a 1.0 version. Then, it would feel like going from the iPhone (1) to the iPhone 4; getting a plethora of new things and features and feel to your iPhone experience, and ...it'd be Christmas with new toys, new capabilities, new look ALL in your hands right there and then.
But instead it is the release of iOS 18 with only a couple minor new items like changing the color of icons, and in a couple months, here's some form of Apple Intelligence (beta-like), and then months later, here is this other new feature, ...drip, drip, drip.
I don't know if Steve would have done this drip-drip release ...to this extent.
The way it goes down now, it is no longer like Christmas when you get your new iPhone and new iOS.
😕
My problem was on YouTube only when I was adding a comment.
It looks okay now but it’s been like that for the past two betas then after a day or two the lag set in again.
Again now it’s okay.
Control centre is completely borked in this beta. It's like going back to mid beta releases of 18.0. Buttons come and go randomly. A reset doesn't help.
Apple doesn’t care (the carriers in China that set up RCS at the carrier instead of depending on Google Jibe are working fine) and Google is not going to piss off T-mobile by saying it’s on them.
Which is why Google decided they can get away with saying it’s Apple‘s fault because Apple’s not going to say anything to the contrary.RCS was a mess before Google. When the US carriers gave up on CCMI, there was literally no way anything better was going to come after that. If I had to guess, I’d say all of the carriers that have MVNO‘s are still sorting out how to manage the much more data (a lot of it for free, mind you) that’s going to be going over their networks with everyone enabled being able to send massively sized reaction gifs hundreds of times a day. And, of course, this is why RCS as an idea failed to get traction from the beginning. The carriers would have to offer a lot and get very little if any real profit from the effort. I would not be surprised if they limited MVNO’s to sending RCS only over Wi-Fi!
The typing lag in the iOS 18 is unbearable. I hope these betas continue to improve on that front. I am using iPhone 16 Pro Max and it is extremely frustrating.
Cute. Not applicable, but cute. Better analogy would be more bakers in a kitchen producing a product.
Last edited by a moderator:
It’s not RCS is a mess it’s the MVNO’s probably don’t want to invest in it.Apple doesn’t care (the carriers in China that set up RCS at the carrier instead of depending on Google Jibe are working fine) and Google is not going to piss off T-mobile by saying it’s on them.
RCS was a mess before Google. When the US carriers gave up on CCMI, there was literally no way anything better was going to come after that. If I had to guess, I’d say all of the carriers that have MVNO‘s are still sorting out how to manage the much more data (a lot of it for free, mind you) that’s going to be going over their networks with everyone enabled being able to send massively sized reaction gifs hundreds of times a day. And, of course, this is why RCS as an idea failed to get traction from the beginning. The carriers would have to offer a lot and get very little if any real profit from the effort. I would not be surprised if they limited MVNO’s to sending RCS only over Wi-Fi!
Why would they as the just rent the lines of the major networks.
A lot of MVNO’s have just got WiFi calling after all these years & plus a lot don’t even offer eSIM
I installed it safely and successfully on my 11” M4 Pro, but it was before they pulled the update, not after. Only a small number of devices are affected, but since it bricked them, they didn’t want to chance it I assume.
I’m typing right now and it hasn’t been fixed. Temp solution is clearing browser history and then I’m able to type normal along with shutting off haptics or sounds.
Good point, as RCS is a burden at this point because they designed/built it for a world where data was prohibitively expensive and allowing more data would just mean more money in their pockets. Even though they started working on it the year the iPhone was released, as it came out in June of that year, it was likely not very clear to the world how far the iPhone and it’s attached unlimited data plan was going to spread. And, unfortunately for the carriers, they weren’t the only ones with dollar signs in their eyes. While they were futzing about, WhatsApp came and basically yanked the consumer market away from them. The 100MB message size built into the spec was no longer going to be a windfall. Customers were not going to accept what the carriers did with MMS, they were going to expect even BETTER service, MORE data, for FREE!
If they’d tied RCS with a more modest 10MB limit, perhaps some carriers would have bit (likely not as the timing still wouldn’t have worked). But, building out infrastructure when no one was going to pay for it and no one was going to switch to a competing carrier that had it (unlike both SMS and MMS before), it was left to languish. If RCS didn’t exist, China would have just created something they could enable WeChat with further. BUT, as all three of the Chinese carriers are on the GSMA board, they likely figured “why not?”
Damn such a shame this even is a bug in the first place. I also noticed a new bug on iOS 18 where I hit the shutter button and it wants to crash the whole phone it seems. Have to hard reboot.
This is exactly my experience. Most Android users I know don't even know what it is, several don't use Google Messenger. Really disappointed but not surprised at Google here.
craig is literally the head of software. You can’t just tell 25,000 people to work on the same problem. Too many cooks in the kitchen. Use your brain.
Is anyone else’s iPhone getting extremely hot on the beta? I just got the “iPhone needs to cool down before you can use it.” message, and I’m barely even doing anything intensive on it. iPhone 12 Pro Max.
the company launching millions of mobile devices has the occasional dud and this qualifies their QC as "absolute trash"?
lmfao. 1st world problems have entitled people to the most absurd opinions.
The MVNO’s are not interested investing in new technologies because that would affect their bottom line why invest in things like RCS or eSIM when the majority of our customers don’t want it.
Ultimately you go to a MVNO because they offer a cheap & basic experience.
Posting the SDK notes as text, link is only a pointer to docs that change with each beta.
General
Known Issues
- Updating from iOS & iPadOS 18 beta 5 to iOS & iPadOS 18.1 beta 1 is not currently supported and will be available in a future iOS & iPadOS 18.1 beta. (133235636)
App Intents
Resolved Issues
- Fixed: Apps that support universal links might not open normally and instead open the browser when the user navigates to a URL provided by the OpenURLIntent or URLRepresentableIntent APIs. (133764689) (FB14784347)
Apple Intelligence
New Features
- When using Apple Intelligence, the new Siri UI might fail to render full screen on large CarPlay displays. (131586542)
Camera Control
Known Issues
- Installing an app with a Capture Extension while another Camera Control app is already selected might cause a momentary system crash. (135021680)
Files
Resolved Issues
- Fixed: Creating local files in the Files app fails in the visionOS 2 and iOS 18 simulators if the host is not upgraded to macOS Sequoia Beta. (132561244)
HealthKit
Resolved Issues
- Fixed: With the introduction of Swift 6 this year, developers who update their projects to use Swift 6 might have issues with their apps, which can lead to app crashes when executing a variety of HealthKit API calls. (131794283)
Lock Screen
Resolved Issues
- Fixed: When on Lock Screen, pulling down to invoke Spotlight does not work. (133404809)
Mail
Known Issues
- Upgrading from iOS 18.0 beta 5 to iOS 18.1 beta might cause all Mail to redownload. (132930689)
Siri
Known Issues
- Siri result snippets might appear in the wrong position. (135035793)
Spotlight
Resolved Issues
- Fixed: Icons in Spotlight might not match icons on the Home Screen. (134088480)
StoreKit
Resolved Issues
- Fixed: The transaction of a successful purchase on the default win-back offer redemption sheet might not appear on Transaction.updates sequence until the next app launch. (133575987)
- Fixed: In StoreKit Testing in Xcode, the offer identifier in the subscription renewal info might be reported incorrectly for offer codes. (133774710)
Swift Charts
Known Issues
- Any project that utilizes Swift Charts fails to build when targeting iOS, macOS, or visionOS. (135905498)
SwiftUI
Resolved Issues
- Fixed: Scene restoration launches the incorrect scene. (132497400)
- Fixed: In apps compiled against SDKs prior to iOS 18.0 and visionOS 2.0, explicit arrow edges are not respected when the app is run on iOS 18.1 or visionOS 2.1. Apps compiled against any macOS SDK will still have the arrow edge respected. (133295608)
- On iOS 18.0, there is a known issue where passing nil to the .preferredColorSchememodifier, after the preferred color scheme is set by a different view in the hierarchy, does not trigger the system color scheme to change. Starting in iOS 18.1, when nil is passed to the .preferredColorScheme modifier, the view indicates no preference for the color scheme and thus uses the system color scheme.
.preferredColorScheme(isDarkMode ? .dark : nil)
The view with the above modifier applied prefers dark mode when isDarkMode is set to true but otherwise defers to the color scheme as determined by the system. (133689390) (FB14768320) - Fixed: Regardless of the deployment target of the app, the popover modifier now does not respect the arrowEdge argument on iOS, iPadOS, or visionOS for apps compiled against iOS 18.1/visionOS 2.1 and run against iOS 18.0/visionOS 2.0. Apps compiled against iOS 18.1/visionOS 2.1 and run against iOS 18.1/visionOS 2.1 do respect the arrowEdge argument. (135231043)
- Now on iOS 18.1, tvOS 18.1 and visionOS 2.1, the View.navigationSplitViewColumnWidth modifier (all overloads) updates dynamically. Previously, the modifier would only be effective once, when applied at the same time the NavigationSplitView was created. If app code was modifying the values passed to navigationSplitViewColumnWidth after the split view was created or logical branches caused .navigationSplitViewColumnWidth to be active after creation, these values now affect column width. As a reminder, though not a changed behavior, on the aforementioned platforms both variants of navigationSplitViewColumnWidth have the same effect, since columns are not user-resizable. (135434989)
Known Issues
- Using if #available in @WidgetBundleBuilder and @SceneBuilder crashes on prior OS versions. (136098106)
Workaround: Disable @WidgetBundleBuilder and @SceneBuilder by using explicit return for if #available checks. For example:
var body: some Widget {
if #available(iOSApplicationExtension 18.0, *) {
return iOS18Widgets
} else {
return existingWidgets
}
}
@available(iOSApplicationExtension 18.0, *)
@WidgetBundleBuilder
var iOS18Widgets: some Widget {
MyNewWidget1()
MyNewWidget2()
existingWidgets
}
@WidgetBundleBuilder
var existingWidgets: some Widget {
MyOldWidgetX()
MyOldWidgetY()
}
WidgetKit
New Features
- A control’s default tint will be set to the App/ extension’s accent color, if a tint is not specified explicitly using the tint(_ modifier. If neither is specified, the control’s tint will be the default system blue tint. (131662481)
Resolved Issues
- Fixed: Rectangular complications and Watch-specific custom Live Activity views use the wrong font metrics, causing title2 and title3 to render much larger than intended and largeTitle to render much smaller than intended. Additionally, custom Live Activity views use the wrong default font (SF Pro instead of SF Compact). (135831317)