Just did an update from MacOS 26b1 to b2 and now the Mail app crashes on launch (Thread 0 - something to do with fonts and the webkit. Happens every time on launch of the Mail app.

I'm trying to make my own MDM server and I'm having trouble allowing nginx to proxy the connection. The web app I'm making can accept http requests so I require nginx. I'm using a certificate from letsencrypt. Every time I try to enroll a phone it instantly rejects at nginx. I have tried multiple cipher options in nginx. I found the following link and my cert supports all except the DHE ones but they say you only need 1. (https://developer.apple.com/forums/thread/128482?answerId=404052022#404052022) What else can I do? 2025/05/21 14:39:44 [info] 105709#105709: *2887 peer closed connection in SSL handshake while SSL handshaking, client: 27.32.155.108, server: 0.0.0.0:9234 2025/05/21 14:41:42 [info] 106014#106014: *2891 peer closed connection in SSL handshake while SSL handshaking, client: 27.32.155.108, server: 0.0.0.0:9234 2025/05/21 14:42:32 [info] 106134#106134: *89 peer closed connection in SSL handshake while SSL handshaking, client: 27.32.155.108, server: 0.0.0.0:9234 2025/05/21 15:09:13 [info] 106132#106132: *124 client timed out (110: Connection timed out) while waiting for request, client: 172.40.1.61, server: 0.0.0.0:9234 below from ssllabs.com upstream backendmdmios { server 172.40.1.61:6744; } server { listen 9234 ssl; http2 on; server_name mdm.domainplaceholder.com; error_log /etc/nginx/logs/ios.com.error.log debug; # error; ssl_certificate /etc/letsencrypt/live/mdm.domainplaceholder.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mdm.domainplaceholder.com/privkey.pem; ssl_protocols TLSv1.2 TLSv1.3; #ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384; ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-CBC-SHA256:ECDHE-RSA-AES128-CBC-SHA:ECDHE-RSA-AES256-GCM-SHA384; #ssl_ciphers TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305; #ssl_protocols TLSv1 TLSv1.1 TLSv1.2; #ssl_ciphers EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4:!3DES:!CAMELLIA; ssl_prefer_server_ciphers on; ssl_dhparam /etc/nginx/dhparams.pem; location / { proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://backendmdmios$request_uri; } }

Hey there, I recently updated my iPhone to the iOS 26 developers beta version, and I’m encountering an issue on the Software Update page. It says “Unable to check for updates,” and I’m unable to revert to iOS 18. Is this a temporary problem? Will I be able to update my iPhone in the future without needing to reset it? Thanks

System data is beyond a joke now. There constant logs being generated and stored somewhere with zero access and ability to delete or clear up. I’ve even tried changing the date hack, however this just created some space from system but mostly just unloaded my apps (a feature which I’ve now disabled, as virtually everything is unloaded now apart from essential items). Apple support says wipe and start again, I’m sure that’s not a solution? Anyone figured out how to resolve this? Also you can’t even force videos into the cloud, frustrating when I’ve got no space and pay for iCloud and have zero space left on my phone. It’s suppose to be intelligent.

since updating from 18.3 to 18.4, both on cellular and WiFi Networks I can’t connect to the internet. Since the phone wont connect to the internet I’m not able to turn off “find my iPhone“ to restore my iPhone to iOS 18.3 this way my iPhone is useless any ideas / thoughts about this?

Hello guys, We have updated our app icon, and it is correctly reflected in our app build and assets. However, the push notification icon is still displaying the old version for some users. ✅ We have verified that: All icon assets in Assets.xcassets match the new icon. The app icon has been updated in Info.plist. The app has been resubmitted and approved on the App Store. ❌ However, some users still see the old notification icon, even after reinstalling the app. Restarting the device does not always resolve the issue. Could you provide insights into how iOS caches notification icons and how we can force a refresh for all users?

In our iOS app we have added example.com in associated domains from the very beginning With no AASA file hosted at example.com domain Now we need a subdomain app.example.com to be intercepted in our app, so for the same, we are thinking to host AASA at app.example.com and add app.example.com in associated domains too. so my question is will hosting AASA at sub domain works? If yes, will it affect older apps where app.example.com is not handled. In short we only want the links with app.example.com to be open in our app not the example.com links

Dear Apple Support Team, I am trying to shared data between two different App target. Target A is main iOS app and Target B is Intent Extension. I have create app group and utilise app group to share data between different target but when setting the user default from Target B stile getting container null. Target B UserDefault object details sharedDefaults UserDefaults 0x0000600000c05110 baseNSObject@0 NSObject kvo id 0x0 0x0000000000000000 [0] id identifier __CFString * "group.com.xxxx. xxxx" 0x0000600001704900 container __CFString * NULL 0x0000000000000000 _volatileDomainNames id 0x0 0x0000000000000000 [0] id Code snippet in Target B to setting UserDefault guard let sharedDefaults = UserDefaults(suiteName: SharedUserDefaults.suitName)else { completion(MuteIntentResponse(code: .failure, userActivity: nil)) return } ///["event": AudioCommand.mute.rawValue] sharedDefaults.set("test", forKey: SharedUserDefaults.Keys.audioCommand) let didSynchronize = sharedDefaults.synchronize() print("Intent Extension: Wrote Synchronize successful: \(didSynchronize)") guard let command = sharedDefaults.string(forKey: SharedUserDefaults.Keys.audioCommand) else { completion(MuteIntentResponse(code: .failure, userActivity: nil)) return } print("userDef \(command)") While reading UserDefault value in Target A UserDefault object details baseNSObject@0 NSObject isa Class NSUserDefaults 0x01000001efe1a8a9 kvo id 0x0 0x0000000000000000 identifier __CFString * "group.com.xxxx. xxxx” 0x0000600001782200 container __CFString * NULL 0x0000000000000000 _volatileDomainNames id 0x0 0x0000000000000000 [0] id Reading UserDefault value Code if let def = UserDefaults(suiteName: SharedUserDefaults.suitName){ print("commandInfo (def.string(forKey: SharedUserDefaults.Keys.audioCommand))") } Please let me know what I am doing wrong.

Every week or so, mouse driver locks up. The LED laser goes out and none of the buttons operate. It's a generic 7 button USB mouse with my USB keyboard still active. I do not know what precipitates the lockup and a system diagnostic request (Sft-Alt-Ctl-Cmd .) does not seem to yield anything useful. > ps -ef|grep -i mouse 501 579 1 0 Mon01PM ?? 0:04.42 /System/Library/ExtensionKit/Extensions/MouseExtension.appex/Contents/MacOS/MouseExtension code-block so the mouse extension was running at the time. With a "sudo kill -HUP 579" it did not restart. Also, switching to a different mouse did no good. The mouse driver was behaving like it was deadlocked and I didn't know the correct incantation for restarting it. I power cycle reset the box. SO: you have a mouse driver problem it cannot be just me It behaves like a deadlock, but not knowing how to get a mouse driver dump, I cannot tell what lock(s) its waiting for.

Hello, my name is Natalia, I'm Ukrainian. Please tell me how to contact Apple to propose a new development? It's more about a startup.

"TMS-90714: Invalid binary - The app contains one or more corrupted binaries" I am facing this error email from appstore since 15 days now and i tried 49 different things to fix this but it is not fixed. I migrated my app from storyboard controller to swiftUI and tried to submit to appstore and am not seeing the build in testflight and am receving the email error above. Can anyone please help, i will provide the required info, also i can pay couple hundered bucks.

I am new to swift (developer from long ago) and have not been able to resolve an issue with IOS - I am building a text entry box with save / cancel buttons at bottom and a texteditor above all within a fixed size frame. It's all OK on macOS but when I try iOS the space taken by the form weirdly expands (beyond the size of the text editor) and end up pushing the save /cancel buttons below outside view. An extract of the code is here. I have tried all sorts of things like setting frame sizes, line limits, spacers, scrolling disable, but I can't stop the behaviour. Any ideas. Apologies if this is well known or my issue due to inexperience I just can't resolve it. private func editSource(in geometry: GeometryProxy) -> some View { NavigationStack{ Form { Section(header: Text("Source Name")) { TextEditor(text: $newSourceName) .font(.title3) .padding(5) .background( RoundedRectangle(cornerRadius: 10) .fill(.background) ) .textFieldStyle(PlainTextFieldStyle()) .frame(height: 50) .foregroundColor(.primary) .focused($isSourceFocused) } } HStack { Button("Save") { events[eventIndex].source = newSourceName isEditingSource = false isSourceFocused = false disableEdit = false } Spacer() Button("Cancel", role: .cancel) { isSourceFocused = false isEditingSource = false disableEdit = false } } .padding() .layoutPriority(1) } #if os(macOS) .scrollDisabled(true) .padding() .frame(height: 180) .frame(width: 240) .background(.gray) #else .frame(width: 240) .frame(height: 240) #endif .cornerRadius(10) .clipShape(RoundedRectangle(cornerRadius: 10)) .overlay( RoundedRectangle(cornerRadius: 10) .stroke(Color.blue, lineWidth: 1) ) .position(sourceLocation) .offset(x: 0, y: 100) .zIndex(1) .onAppear() { isSourceFocused = true newSourceName = events[eventIndex].source } }

A few days ago I installed beta 1 of macOS 26 Tahoe on a spare MacBook Pro 14-inch M4. Everything went well, and it looks okay (well, I don't like it at all, but hey-ho), and I shut it down. I started it up today, and it rejects my login password every time, then locks my account. When I click the link to "Restart and show password reset options" I'm asked for my Apple ID details, so I enter the correct email and password, then the MBP reboots and I'm back on the login screen with no indication that anything has changed. Guess I'm stuck now... FB18364657

i can’t turn off autofill of an input field from background noise

I have a PIP camera that is streaming from the front and back based on AVCaptureMultiCamSession. It works fine, but when i go to swap the camera it crashes. This is code that works with a single camera, so not sure what is wrong. Also the object appears valid in the debugger. This is the snippit where the camera is swapped private func updateSessionConfiguration() { guard isCaptureSessionConfigured else { return } captureSession.beginConfiguration() defer { captureSession.commitConfiguration() } // Remove all current inputs for input in captureSession.inputs { if let deviceInput = input as? AVCaptureDeviceInput { captureSession.removeInput(deviceInput) app_log("removing input for \(input)") } } // Add the primary device input if let deviceInput = deviceInputFor(device: captureDevice) { app_log("device input \(deviceInput)") if !captureSession.inputs.contains(deviceInput), captureSession.canAddInput(deviceInput) { captureSession.addInput(deviceInput) } } if let secondaryDeviceInput = deviceInputFor(device: secondaryCaptureDevice) { app_log("Secondary device input \(secondaryDeviceInput)") if !captureSession.inputs.contains(secondaryDeviceInput), captureSession.canAddInput(secondaryDeviceInput) { captureSession.addInput(secondaryDeviceInput) } } updateVideoOutputConnection() } It crashes at: captureSession.addInput(deviceInput) with: Thread 10: EXC_BAD_ACCESS (code=1, address=0xcaeb36b964f0) which is strange because canAdd is checked prior to this call. Totally stumped here. Please help. Not sure if this is an AVCaptureMuliCamSession issue or something.

I'm totally baffled by the changes Apple made on iOS18 about certificates usage in the built-in mail application. They decided that self-signed are not accepted any more, fine. As long as you can install your own root CA and trust it, it should be fine. But NO! They have also decided that mail will only accept IMAP servers using a domain name, no more just and IP address. So you can't get any IP-based certificate that will be accepted by the mail app, even with the right SAN and al. I've tried two "identical" certs, one with a domain and one with an IP and the domain works while the IP fails, being rejected as non-valid by the app. The most funny part is that the IP cert is good enough to configure mail (can see the successful login), but is being rejected when reading emails. I'm really fed up with the "Apple police" that wants to push us not using our own storage anymore. My se case is simple, I have an IMAP server that is used by family to archive all emails and keep them organized, saved forever and away from being scanned. I need to access that server either when locally connected or through VPN. For VPN, I use split tunnels because I don't want all traffic to go to tunnel. Nor do I want to create my own local DNS server and have all VPN clients use such DNS server only for the sake of having a domain name for the IMAP server. Nor do I want to open an external port to redirect to my IMAP server (that works of course as then I can use DDNS ...). Talk about increased security! This is insane

This wasn't happening until I updated Xcode to 16.2 (I'm using Sequoia 15.2). When I run any Mac app, I get these errors: Can't find or decode reasons Failed to get or decode unavailable reasons Can't find or decode disabled use cases I even got these errors running "Hello, world" which tells me that either I need to reinstall or there is a bug. Thanks for any help, -Ashley

I downloaded Xcode Beta 26 and built the POS code repository project. However, an error appeared: unable to find the module dependency 'minizip'. No changes have been made to the repository since upgrading to iOS 18.0. Is this a new issue with Xcode 26, and what are the resolution steps?

Hi Guys! I’ve been encountering some issues while testing the latest iOS beta. Is anyone else experiencing similar bugs? Test environment: Device enrolled in iOS 26 Beta since June 9th, 5:00 PM (BRT) Hardware-related issues: • The device is overheating during routine tasks, especially when screen brightness is set to maximum. • Battery life has dropped significantly — approximately 20% to 30% shorter compared to iOS 18.5 UX/UI issues: • Scrollbars occasionally behave erratically in some apps — scrolling leads to empty areas or becomes unresponsive. • When opening a new tab in Safari, the app sometimes freezes and requires a force restart. • The Control Center is difficult to interact with due to excessive transparency, which gives the impression that the icons are scattered without visual hierarchy.

The Uber Driver app is able to get background location and there’s no way to turn it off from settings. Unlike other apps where there’s always an option to turn off background location from settings. Is this a bug or special treatment for big companies? this matters to me because we’re in a similar business but our app has to request background permissions, explicitly. I am attaching both of the screenshots here for you to compare and see. Please note that I verified personally that Uber Driver app is able to get background location.