Apple come on release iOS 18.2 bata 4 today Apple come on release iOS 18.2 bata 4 today and not tomorrow because i can not wait

We are experiencing thousands of crashes in our application when attempting to present the camera through a Web View. The app crashes during this process, and the crash logs point to WebCore::AVVideoCaptureSource::create WebCore::RealtimeMediaSourceCenter::getUserMediaDevices. This issue has only been observed in iOS 18.2 beta versions (beta 1 - 22C5109p, beta 2 - 22C5125e, beta 3 - 22C5131e). In iOS versions below 18.2, the functionality works and we haven't identified any correlation with specific device models. The problem seems to stem from a WebCore framework introduced in these beta releases 18.2. We kindly request a review and fix for this issue in upcoming beta releases to restore functionality. Let us know if there are any workarounds or adjustments we can implement in the interim. Thank you for your attention to this matter.

Hello team, I am using USBDriverKit and Driverkit framework in my application for communication of USB device. After updating my iPad OS to 18 public beta, I am unable to get option to enable drivers in my setting page of my application. However, I am able to see that options in developer beta version of iPad OS 18. Can anyone guide me, how should I proceed further as I am unable to use my USB devices.

I'm currently using Xcode 16 Beta (16A5171c) and I'm getting a crash whenever I attempt to fetch using my ModelContext in my SwiftUI video using the environment I'm getting a crash specifically on iOS 18 simulators. I've opened up a feedback FB13831520 but it's worth noting that I can run the code I'll explain in detail below on iOS 17+ simulator and devices just fine. I'm getting the following crash: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'The specified URI is not a valid Core Data URI: x-coredata:///MyApp/XXXXX-XXXXX-XXXX-XXXX-XXXXXXXXXXXX' It's almost as if on iOS18 SwiftData is unable to find the file on the simulator to perform CRUD operations. All I'm doing in my project is simply fetching data using the modelContext. func contains(_ model: MyModel, in context: ModelContext) -> Bool { let objId = palette.persistentModelID let fetchDesc = FetchDescriptor<MyModel>(predicate: #Predicate { $0.persistentModelID == objId }) let itemCount = try? context.fetchCount(fetchDesc) return itemCount != 0 }

I updated today at Xcode 16 beta 6, and my app using SwiftData on iOS 18 (beta 6) is getting now this new error when saving the model in the modelContext. I don't understand if it is a regression introduced in the beta 6 or if it is enforced something that previously wasn't. It seems to be always referred to the ID property, for example: SwiftData/ModelCoders.swift:1762: Fatal error: Passed nil for a non-optional keypath \MyModel.id In this case (and in most of the cases in my models) the ID is defined as following @Attribute(.unique) public var id: UUID I also tried to add the initialization inline, but didn't help @Attribute(.unique) public var id: UUID = .init() I also tried to remove the @Attribute(.unique), didn't help as well. Does any of you have the same issue?

Prior to iOS 18.1, App-prefs:Wallpaper deeplinked to the wallpaper settings. On iOS 18.1, it now deeplinks to the settings app. Is there a new URL to deeplink to the Wallpaper settings? The following URLs have been tested and do not work on iOS 18.1: App-prefs:Wallpaper App-prefs:wallpaper App-prefs:root=wallpaper App-prefs:root=Wallpaper App-prefs:root=WALLPAPER App-prefs:root=General&path=Wallpaper prefs:root=Wallpaper

I'm using SwiftData to persist my items in storage. I used .modelContext to pass in my shared context, and on iOS 18 (both on a physical device and a simulator), I discovered a bug where SwiftData doesn't automatically save my data. For example, I could add a new item, go to the next screen, change something that reloads a previous screen, and SwiftData just forgets the item that I added. Please find the fully working code attached. While writing this post, I realized that if I use .modelContainer instead of .modelContext, the issue is solved. So I have two questions: It seems like .modelContainer is the go-to option when working with SwiftData, but why did an issue occur when I used .modelContext and passed in a shared container? When should we use .modelContext over .modelContainer? What was the bug? It's working fine in iOS 17, but not in iOS 18. Or is this expected? Here's the fully working code so you can copy and paste: import SwiftUI import SwiftData typealias NamedColor = (color: Color, name: String) extension Color { init(r: Double, g: Double, b: Double) { self.init(red: r/255, green: g/255, blue: b/255) } static let namedColors: [NamedColor] = [ (.blue, "Blue"), (.red, "Red"), (.green, "Green"), (.orange, "Orange"), (.yellow, "Yellow"), (.pink, "Pink"), (.purple, "Purple"), (.teal, "Teal"), (.indigo, "Indigo"), (.brown, "Brown"), (.cyan, "Cyan"), (.gray, "Gray") ] static func name(for color: Color) -> String { return namedColors.first(where: { $0.color == color })?.name ?? "Blue" } static func color(for name: String) -> Color { return namedColors.first(where: { $0.name == name })?.color ?? .blue } } @main struct SwiftDataTestApp: App { var sharedModelContainer: ModelContainer = { let schema = Schema([ Item.self, ]) let modelConfiguration = ModelConfiguration(schema: schema, isStoredInMemoryOnly: false) do { return try ModelContainer(for: schema, configurations: [modelConfiguration]) } catch { fatalError("Could not create ModelContainer: \(error)") } }() @AppStorage("accentColor") private var accentColorName: String = "Blue" var body: some Scene { WindowGroup { NavigationStack { HomeView() } .tint(Color.color(for: accentColorName)) } .modelContainer(sharedModelContainer) // This works // .modelContext(ModelContext(sharedModelContainer)) // This doesn't work } } @Model final class Item { var timestamp: Date init(timestamp: Date) { self.timestamp = timestamp } } struct HomeView: View { @State private var showSettings = false @Environment(\.modelContext) var modelContext @AppStorage("accentColor") private var accentColorName: String = "Blue" @Query private var items: [Item] var body: some View { List { ForEach(items) { item in NavigationLink { Text("Item at \(item.timestamp, format: Date.FormatStyle(date: .numeric, time: .standard))") } label: { Text(item.timestamp, format: Date.FormatStyle(date: .numeric, time: .standard)) } } Button { withAnimation { let newItem = Item(timestamp: Date()) modelContext.insert(newItem) } } label: { Image(systemName: "plus") .frame(maxWidth: .infinity) .frame(maxHeight: .infinity) } } .navigationTitle("Habits") .toolbar { ToolbarItem(placement: .navigationBarTrailing) { Button(action: { showSettings = true }) { Label("", systemImage: "gearshape.fill") } } } .navigationDestination(isPresented: $showSettings) { colorPickerView } } private var colorPickerView: some View { Form { Section(header: Text("Accent Color")) { Picker("Accent Color", selection: $accentColorName) { ForEach(Color.namedColors, id: \.name) { namedColor in Text(namedColor.name) .tag(namedColor.name) .foregroundColor(namedColor.color) } } .pickerStyle(.wheel) } } .navigationTitle("Settings") } }

I noticed that the ChatGPT is listed as an "Extension" in the Apple Intelligence settings on iOS 18.2 beta. Does this mean developers will be able to create their own extensions? Or will this be limited to larger companies to incorporate their own models into Apple Intelligence?

The application I work on has a webview in it and I found after updating my iPad to the iOS 18.2 beta it no longer detects clicks properly. The same build works fine on other iOS devices not on the beta. When the webview refreshes it works normally until I interact with any other element of the application and then it stops recognizing click inputs. It can still scroll and zoom normally though. I've tested this against 2 different web view packages and different web pages and the issue is consistent. Has anyone else seen anything like this?

Hey, There's like this darkish line on my iPhone and iPad when I open the Photos app. This scared the ding dong out of me the first time I saw it but then I realized in was a software issue when it disappeared as I swiped up to close the app. It's really weird because it's extremely faint but I can't seem to catch it in screenshots. I know for a fact this is a software issue because it doesn't show up in any other apps. It also changes from horizontal to vertical depending on how I turn my iPhone. Can everyone please just check your own iPhone or iPad to make sure I'm not the only one? I'm on the 18.2 developer beta by the way. Thanks!

Not sure if I am in the right place, directed here by apple support staff. On starting my MacBook Pro M3 Max this morning it went into a cycle of rebooting after about 1-2 mins. I managed to see the following error message "SODC report detected: AP watchdog expired" before the screen went totally black and the fans went to full speed. Any thoughts on this? Sequoia 15.2, no external drives or hardware plugged in. Thanks

Phone glitchs a lot more my flashlight won’t turn on half the time even when it says it’s on its not on settings page likes to freeze randomly will restart my phone as well and controller has more issues connecting on certain games

I have seen lots of complaints about the phone app and how things don’t run as smoothly, and stuff about the shade of the tapback feature icons. I personally have been struggling with replying now that I can’t just double tap. I also don’t like that when I pull down on a message, I can’t copy the messages anymore. I have to use Duo Mobile for school, and my mom will sometimes log in to help with my loan, and I have to have a code to log her in, it used to be easy to just pull down and copy but now have to go into messages. Very small inconveniences, and I will eventually be able to get used to them once they become habit, but I’d rather not have to adapt lol.

Really stumped on this issue my team is seeing with the Xcode 16 Beta (both Xcode 16 version 6 and Xcode 16.1). Wondering if anyone was having a similar issue and if this is a bug or something configured incorrectly. Basically, when I go to build settings and search for anything related to "Swift Compiler" nothing shows up. The only thing that appears with "Swift" in the title is under the User Defined keys (see attached) As such, I'm unable to change the Swift version for the project and I'm stuck in Swift 6 language mode which we're not quite ready for yet. This is only occurring on one of our targets. Our other app projects are behaving as expected. The project in question has the main target we build the project with and 2 support frameworks. The supporting frameworks are also working correctly. Its just the primary build target giving us fits. Curious if anyone is seeing something similar or has suggestions. Thanks!

I installed MacOS Sequoia 15.2 Beta 3 this morning. It worked fine till the afternoon but after that, I could no longer connect to the internet. I was able to join wifi networks and hotspots but it would just show no internet connection. Tried connecting via iPhone USB and LAN too but wasn't able to get it to work. Finally with no other option had to reinstall mac os. Gladly, the recovery tool installed the Beta 2. Learned my lesson, would never upgrade to developer beta ever again (at least not on my work laptop).

Hello, Im am running Sequoia 15.2 beta. When my screensaver starts en i move my mouse the screen turns black and i only see my mouse pointer. Further nothing happens and i need to force reboot my macbook pro m1. Is this a familiar issue or does any one know what to do in this case? Kind regards, Martin

problem wifi and bluethoot no working

I have a problem where my Anker 321 MagGo stopped charging my iPhone 15 Pro wirelessly. I can charge it via cable, but I can't use Magsafe. I think it can be about the IOS 18.2 Beta 2 update, but I'm not sure. Is there anyone have the same problem? Or do you have any suggestions for me?

Here’s a suggestion: Apple should provide a feature for iPhone users to automatically log the specific time and date whenever they reset their phone. This log would allow users to easily track when resets occur. Additionally, Apple could enhance backup options by enabling users to restore any data lost during a reset. This might include automatic backups before each reset or a more intuitive process for recovering previously backed-up data.

Here are some reasons why Apple should consider an update to enhance message refreshing and chat sharing on WhatsApp, making it smoother across both iPhone and Android: Cross-Platform Compatibility • Problem: Right now, switching between iPhone and Android on WhatsApp can result in lost messages or complicated backup processes due to differences in operating systems and data formats. • Impact: A universal update allowing seamless message refresh and sharing would bridge the gap between iOS and Android. Users could switch devices without losing conversation history, making the experience more fluid and inclusive for both iPhone and Android users. Enhanced Data Security and Privacy • Problem: Many users rely on third-party methods to back up or transfer WhatsApp chats, which can pose privacy risks. • Solution: A unified system from Apple (and Android) could ensure that all backups and chat transfers are encrypted, keeping data private and secure, aligned with each platform’s commitment to data protection. • Impact: This would reduce security concerns for people using their devices for sensitive communications, such as business transactions or personal matters. Peace of Mind for Users • Problem: Many users worry about losing important messages when they upgrade their phones or change their operating systems. • Solution: An update that includes auto-refresh and universal chat-sharing across backups would make sure conversations and media are always accessible, no matter the device. • Impact: This peace of mind would lead to higher user satisfaction and reduce anxiety about data loss, enhancing WhatsApp’s reliability as a communication platform worldwide. Improved User Experience and Retention • Problem: The complexity of transferring chats between iOS and Android devices can push users to avoid switching or even consider alternatives to WhatsApp. • Solution: With a streamlined message and chat-sharing experience, users would find it easier to stay connected on WhatsApp, regardless of the device. • Impact: This could increase user retention and trust, making WhatsApp more indispensable as a global messaging platform. Greater Accessibility for Global Users • Problem: Many users globally use WhatsApp for family, work, and community connections, especially in areas where it is the primary communication tool. Losing messages or finding backup systems challenging can cause disruptions. • Solution: A message refresh and sharing update would support seamless transitions and backups, making WhatsApp more accessible and consistent. • Impact: This would support worldwide connectivity, especially in regions where WhatsApp is a lifeline for communication, fostering inclusivity and reducing digital barriers. Future-Proofing for Technological Advancements • Problem: As technology advances, the gap between iOS and Android compatibility could widen if not addressed now. • Solution: An update that includes flexible chat-sharing and message-refreshing capabilities would keep Apple and Android devices aligned and prepared for future features or communication needs. • Impact: This proactive approach ensures that WhatsApp remains relevant, adaptable, and future-ready for global users as both platforms evolve. Overall, this update could foster better communication, security, and user satisfaction worldwide. It would also help Apple and WhatsApp strengthen their roles as leaders in secure and universal messaging solutions.