I'm trying to disable Writing Tools for a specific TextField using .writingToolsBehavior(.disabled), but when running the app on my iPhone 16 Pro with Apple Intelligence enabled, I can still use Writing Tools on the text box. I also see no difference with .writingToolsBehavior(.limited). Is there something I'm doing wrong or is this a bug? Sample code below: import SwiftUI struct ContentView: View { @State var text = "" var body: some View { VStack { TextField("Enter Text", text: $text) .writingToolsBehavior(.disabled) } .padding() } } #Preview { ContentView() }

Ever since updating both my iPhone and iPad to iOS 18.1 beta 7, they simply won't connect to Xcode 16.1 beta 3. When connecting via cable, Xcode gets stuck on preparing for 5 to 10 mins and then outputs the below error: The developer disk image could not be mounted on this device. Domain: com.apple.dt.CoreDeviceError Code: 12040 Failure Reason: The caller does not have permission to perform the specified operation. User Info: { DDIPath = "/Library/Developer/DeveloperDiskImages/iOS_DDI.dmg"; DVTErrorCreationDateKey = "2024-10-15 9:06:17\U202fpm +0000"; DeviceIdentifier = "63EC7037-121B-4E79-9553-952A09720DAC"; NSURL = "file:///Library/Developer/DeveloperDiskImages/iOS_DDI.dmg"; Options = { MountedBundlePath = "file:///private/var/tmp/CoreDevice_DDI_Staging_501/63EC7037-121B-4E79-9553-952A09720DAC/"; UseCredentials = 0; }; "com.apple.dt.DVTCoreDevice.operationName" = enablePersonalizedDDI; } -- The caller does not have permission to perform the specified operation. Domain: com.apple.dt.CoreDeviceError Code: 2 -- Error mounting image: 0xe8000109 (kAMDMobileImageMounterNetworkForbiddenError: A network error occurred (forbidden).) Domain: com.apple.mobiledevice Code: -402652919 User Info: { FunctionName = AMDeviceRemoteMountPersonalizedBundle; LineNumber = 2145; } -- AMAuthInstallRequestSendSync failed: 3503 (kAMAuthInstallErrorHTTPForbidden) Domain: com.apple.mobiledevice Code: -402652919 User Info: { FunctionName = "-[PersonalizedImage mountImage:]"; LineNumber = 2042; } -- System Information macOS Version 15.0.1 (Build 24A348) Xcode 16.1 (23502) (Build 16B5029d) Timestamp: 2024-10-15T22:06:17+01:00 Any solution for this issue?

I have a Safari extension which allows the user to load their own homepage upon opening a new tab. The extension works by retrieving the homepage URL from UserDefaults and then redirecting to it using window.location.replace. In iOS 18, if the homepage is unable to be loaded due to, for example the user having no internet connection, Safari will go into an rapid loading loop, which eventually stops after a while. This is unlike iOS 17, where trying to reproduce the same scenario will end up with a Safari error page, which should be the expected behaviour. In short, instead of Safari going into an infinite loading loop, it should display a Safari error page like iOS 17 does. As this issue is only happening on iOS 18, I am almost certain it's an iOS bug and would appreciate if this can be fixed as soon as possible. I have created a Feedback Assistant report with ID FB15853821, which contains a sysdiagnose file from my iPhone 16 Pro, as well as two videos, one from my iPhone 16 Pro with iOS 18.2 beta 3 and the other video showing a comparison between iOS 18 and 17. Both videos first show the extension functioning correctly with an active internet connection, but when I disable my internet, the iOS 18 Safari goes into an infinite loop. Here are the steps to reproduce the issue: Download the Homepage for Safari app from the App Store: https://apps.apple.com/gb/app/homepage-for-safari/id6481118559 Enter any valid homepage URL, such as https://apple.com and tap Save Go to Settings -> Apps -> Safari -> Extensions -> Homepage and enable the extension Make sure Open New Tabs is set to “Homepage” Turn off both WiFi and cellular data and attempt to open a new tab in Safari Please note that this also happens with iOS 18.2 beta 4.

I've been trying to upload my app to the App Store with Xcode 16.3 RC but I keep getting these error messages. When will Apple start allowing Xcode 16.3 submissions?

I have been experimenting with the BGContinuedProcessingTask API recently (and published sample code for it https://github.com/infinitepower18/BGContinuedProcessingTaskDemo) I have noticed that if I lock the phone, the code that runs as part of the task stops executing. My sample code simply updates the progress each second until it gets to 100, so it should be completed in 1 minute 40 seconds. However, after locking the phone and checking the lock screen a few seconds later the progress indicator was in the same position as before I locked it. If I leave the phone locked for several minutes and check the lock screen the live activity says "Task failed". I haven't seen anything in the documentation regarding execution of tasks while the phone is locked. So I'm a bit confused if I encountered an iOS bug here?

In iOS Background Execution limits, I see this: When the user ‘force quits’ an app by swiping up in the multitasking UI, iOS interprets that to mean that the user doesn’t want the app running at all. iOS also sets a flag that prevents the app from being launched in the background. That flag gets cleared when the user next launches the app manually. However, I see that when I close an app on iPadOS 26 with the red X, the app doesn't appear in the multitasking UI. So are they treated as force closes and prevented from running background tasks?

I'm currently working on a SwiftUI subscription manager app and getting ready to launch my first TestFlight beta soon. Things are going well so far, the only thing I'm having trouble figuring out is how to schedule notifications based on a subscription start date, as well as calculating the next renewal date. Upon adding a subscription, the user will be able to specify a start date, whether it renews weekly, monthly or annually as well as when the notification should be sent. The user can choose between being notified on day of renewal to 7 days before renewal. I also need a way to calculate the date of next renewal. The next renewal date will not be stored, only the start date. I've been thinking to solve this by getting the next trigger date of the notification, as well as accounting for how many days before renewal. It would be really appreciated if someone knows the solution to this problem.

I am trying to set the background colour of my app shortcut platter for the visionOS version using NSAppIconComplementingColorNames but it doesn’t take effect when I check the shortcuts app. I see the built in Music Recognition app has a background colour but I am unable to set one for my app. Please note that this feature is working correctly on iOS. But on visionOS it has no effect and returns a plain background. I am using Xcode 15.3 beta 2 and running the visionOS 1.1 simulator. Sample code from Info.plist: <key>CFBundleIcons</key> <dict> <key>CFBundlePrimaryIcon</key> <dict> <key>NSAppIconComplementingColorNames</key> <array> <string>SMGreen</string> <string>DarkGreen</string> </array> </dict> </dict> Feedback ID: FB13595442

If an app contains app intents and built using the visionOS 1.1 SDK, and the app is either run on the visionOS 1.0 simulator or a visionOS 1.0 device the app instantly crashes on launch with a missing symbol error. This doesn’t happen with apps built using the visionOS 1.0 SDK. Below is a screenshot of a crash report sent by TestFlight review: Feedback ID: FB13666685

I have a native SwiftUI Mac app which is based off my iOS app and includes Core Data with iCloud sync. As per my understanding, when a user makes a change on one of the devices a remote notification is sent to the others. I have a widget which displays information from Core Data and the remote notification makes the widget update its information on the next timeline refresh without the user having to open the app manually. My question is, if an app is closed on macOS so it's not even running in the Dock, do remote notifications work? This page says "the delegate receives this message when the application is running and a remote notification arrives for it". Does that mean the app won't receive remote CloudKit notifications when closed on macOS?

On both the iOS 18 beta 3 and iPadOS 18 beta 3 simulators, the customise button in home screen edit mode does nothing. I can check the dark mode icons by toggling the system appearance, but as the customise menu doesn’t work there is no way to check the tinted icons on the simulator. Feedback ID: FB14422030

I integrated the image playground sheet in my app, however when I select Take Photo on the iOS version of my app it just reloads the sheet. After several attempts I get the below error message. This issue doesn’t occur on the macOS version of my app, where it first requests camera permission before allowing me to take the photo. I’m not sure if this is happening because I don’t request the camera permission anywhere in my app. My app doesn’t use the camera at all apart from the Take Photo feature which is part of the image playground sheet. Feedback ID: FB15591786

I use the write-review query parameter in my App Store URL to bring up the review prompt in the App Store app: https://apps.apple.com/app/id0123456789?action=write-review (0123456789 is just an example ID, obviously replace that with your app ID) This is exactly what is supposed to be done as per the documentation: https://developer.apple.com/documentation/storekit/requesting_app_store_reviews#4312600 However, on macOS it just opens the product page as if I never put the query parameter in the URL. It works fine on iOS 18.2. I am using macOS 15.2 beta 3 (24C5079e) Feedback ID: FB15866683

I don't have any Apple TV apps. Somehow, I see a few downloads of my app on Apple TV. As far as I understand, Apple TV cannot run anything other than apps made for the tvOS platform. So I'm confused why I'm seeing this in my analytics.

I noticed the time sensitive entitlement says it's only for iOS and macOS. But without the entitlement, the time sensitive toggle doesn't show in my app's notification settings on visionOS. When I archive my visionOS app for App Store Connect, the entitlement seems to be taken out as it doesn't show in my entitlement list for the build in App Store Connect. I'm confused at this point if the entitlement is really necessary, since it seems to be needed to debug on the simulator at least. I don't have a physical device to test it on unfortunately.