Here is an App using CoreML API with ML package format, it works fine in iOS17, while it is crashed when calling [MLModel modelWithContentsOfURL ] to load model running in iOS18. It seems an exception is raised "Failed to set compute_device_types_mask E5RT: Cannot provide zero compute device types. (1)". Is it a bug of iOS18 beta version , and it will be fixed in the future?
The stack is as below:
Exception Codes: #0 at 0x1e9280254
Crashed Thread: 49
Application Specific Information:
*** Terminating app due to uncaught exception 'NSGenericException', reason: 'Failed to set compute_device_types_mask E5RT: Cannot provide zero compute device types. (1)'
Last Exception Backtrace:
0 CoreFoundation 0x0000000199466418 __exceptionPreprocess + 164
1 libobjc.A.dylib 0x00000001967cde88 objc_exception_throw + 76
2 CoreFoundation 0x0000000199560794 -[NSException initWithCoder:]
3 CoreML 0x00000001b4fcfa8c -[MLE5ProgramLibraryOnDeviceAOTCompilationImpl createProgramLibraryHandleWithRespecialization:error:] + 1584
4 CoreML 0x00000001b4fcf3cc -[MLE5ProgramLibrary _programLibraryHandleWithForceRespecialization:error:] + 96
5 CoreML 0x00000001b4fc23d8 __44-[MLE5ProgramLibrary prepareAndReturnError:]_block_invoke + 60
6 libdispatch.dylib 0x00000001a12e1160 _dispatch_client_callout + 20
7 libdispatch.dylib 0x00000001a12f07b8 _dispatch_lane_barrier_sync_invoke_and_complete + 56
8 CoreML 0x00000001b4fc3e98 -[MLE5ProgramLibrary prepareAndReturnError:] + 220
9 CoreML 0x00000001b4fc3bc0 -[MLE5Engine initWithContainer:configuration:error:] + 220
10 CoreML 0x00000001b4fc3888 +[MLE5Engine loadModelFromCompiledArchive:modelVersionInfo:compilerVersionInfo:configuration:error:] + 344
11 CoreML 0x00000001b4faf53c +[MLLoader _loadModelWithClass:fromArchive:modelVersionInfo:compilerVersionInfo:configuration:error:] + 364
12 CoreML 0x00000001b4faedd4 +[MLLoader _loadModelFromArchive:configuration:modelVersion:compilerVersion:loaderEvent:useUpdatableModelLoaders:loadingClasses:error:] + 540
13 CoreML 0x00000001b4f9b900 +[MLLoader _loadWithModelLoaderFromArchive:configuration:loaderEvent:useUpdatableModelLoaders:error:] + 424
14 CoreML 0x00000001b4faaeac +[MLLoader _loadModelFromArchive:configuration:loaderEvent:useUpdatableModelLoaders:error:] + 460
15 CoreML 0x00000001b4fb0428 +[MLLoader _loadModelFromAssetAtURL:configuration:loaderEvent:error:] + 240
16 CoreML 0x00000001b4fb00c4 +[MLLoader loadModelFromAssetAtURL:configuration:error:] + 104
17 CoreML 0x00000001b5314118 -[MLModelAssetResourceFactoryOnDiskImpl modelWithConfiguration:error:] + 116
18 CoreML 0x00000001b5418cc0 __60-[MLModelAssetResourceFactory modelWithConfiguration:error:]_block_invoke + 72
19 libdispatch.dylib 0x00000001a12e1160 _dispatch_client_callout + 20
20 libdispatch.dylib 0x00000001a12f07b8 _dispatch_lane_barrier_sync_invoke_and_complete + 56
21 CoreML 0x00000001b5418b94 -[MLModelAssetResourceFactory modelWithConfiguration:error:] + 276
22 CoreML 0x00000001b542919c -[MLModelAssetModelVendor modelWithConfiguration:error:] + 152
23 CoreML 0x00000001b5380ce4 -[MLModelAsset modelWithConfiguration:error:] + 112
24 CoreML 0x00000001b4fb0b3c +[MLModel modelWithContentsOfURL:configuration:error:] + 168
Posts under Beta tag
200 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
When creating a plain window in SwiftUI on macOS 15.0 beta, the TextEditor within the window does not accept keyboard input. I suspect it's because plain windows cannot become key windows.
Here is a minimal example:
import SwiftUI
struct ContentView: View {
@State var text: String = "Hello World"
var body: some View {
VStack {
TextEditor(text: $text)
}
}
}
@main
struct BigTextApp: App {
var body: some Scene {
Window("Text Window", id: "TextWindow") {
ContentView()
}
.windowStyle(.plain)
}
}
Attempting to type gives the following warning in Xcode: Warning: -[NSWindow makeKeyWindow] called on SwiftUI.AppKitWindow which returned NO from -[NSWindow canBecomeKeyWindow].
Is there a way to make the window capable of becoming a key window without dropping down to UIKit? Or is there another way to allow the TextEditor to accept keyboard input?
I have tried focusing the TextEditor, but that didn't work.
Hello everyone. Is iPadOS18’s Eye-tracking feautre available on iPad Pro 12.9” 2018? If not, where can I find the compatible devices where Eye-tracking available?
In the XCode 16 beta, it isn't possible to create a new StoreKit configuration file because the templates list doesn't contain that option.
Adding the storekit extension to a file crashes XCode or doesn't have an effect at all. But, loading an existing file still works.
I try Control Widget
I check API availability like this
don't work WidgetBundleBuilder.buildBlock()
so i use ControlWidgetConfigurationBuilder.buildBlock ! but it didn't work too
what should i do ?
Hello im on IPadOS 18 developer beta version 1 and when i connect to my managed wallpaper instead of it changing the wallpaper to the managed one it becomes plain green, how do i fix this
I have watched the following WWDC 2024 sessions:
What’s new in SwiftData
Create a custom data store with SwiftData
Platform State of the Union
Now, I have an application that exposes a GraphQL API endpoint that's using PostgreSQL Server 16.3 database. Next, this API returns JSON to the client application (i.e. SwiftUI app). Furthermore, I have checked the current documentation and the above videos appear to be the best reference at this time.
My proposed architecture looks like the following:
SwiftUI <-->
SwiftData <-->
PostgreStoreConfiguration && PostgreStore TBD <-->
GraphQL API <-->
PostgreSQL
Thus, I have the following questions:
Are there plans to add common out-of-the-box data store implementations for PostgreSQL, Cassandra, Redis, and so on?
Will it be possible to implement data stores built to use gRPC, GraphQL, REST, and others to name a few?
Will there be more documentation on the actual creation of a custom data store because the current documentation provides a slim API reference?
I look forward to your feedback regarding the SwiftData custom data stores.
Here is the project https://github.com/devMEremenko/XcodeBenchmark
Hello!
So I updated my mac to 15.0 Sequoia Developer Beta and couldn't run Xcode 15.4 because of the Mac version mismatch, so I installed Xcode 16 beta and archived my app, but of course I cannot publish it to App Store because Apple doesn't let you do it with beta soft.
So, I downloaded Xcode 15.4 (current latest stable build) and managed to run it following this fix: https://stackoverflow.com/questions/69994916/how-can-i-run-older-xcode-version-on-new-macos-version
But, now when I create a new archive and submit it for review I am getting:
ITMS-90111: Unsupported SDK or Xcode version - App submissions must use the latest Xcode and SDK Release Candidates (RC). For details on currently supported versions, visit: https://developer.apple.com/news/releases.
I tried deleting derived data and build folders, building new archives, but to no avail.
Has anybody encountered this before?
I'm looking at the new beta features for MapKit in SwiftUI, does anyone know if it's possible to create a map annotation callout or popover from a custom view?
macOS 15 (beta) has borked my desktop, changing a longstanding Dock behavior (for the worse); Apple says it’s expected behavior. :(
I wonder if anyone else is affected by this change.
I have my displays positioned as shown in the attached Screenshot, with a 4K BENQ Thunderbolt Display positioned above the internal display of an M2 MacBook Air.
Prior to macOS 15, I was able to place the dock at the bottom of the upper display using the technique described here https://apple.stackexchange.com/a/208750 This allows taking advantage of the much greater real estate on the external display.
As of macOS 15 (WWDC developer beta), this no longer works, and I can find no way to move the dock to the upper external display, and my dock remains squeezed into the tiny space available on my internal display (see attached photo).
Hey,
So I obviously downloaded the dev beta the second I could, and I didn’t notice any bugs. Except after the first reboot, the new Screen Time settings UI is replaced by the old one (see video below). This also has an effect on Remote Screen Time Management somehow, making any change (Downtime, App limit, etc) from the guardian’s device over the internet (as in not directly on the managed phone) not take effect at all. Rebooting does nothing, connecting to wifi does nothing, everything. I reported this to the Feedback Assistant so hopefully they catch wind of this soon.
Anyone else experiencing this bug or does anyone have a workaround? Reply if so.
Thanks,
Mr. Sharky
Xcode 16 beta, installed on a macOS 15 beta VM, on macOS 14.5 host, does not let me log into my account. 'An unknown error occurred' after entering password.
Can't open or create a project.
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
}
The following videos from WWDC24 say that we can use cloud storage for our SwiftData stores. Video references below:
What's new in SwiftData
Create a custom data store with SwiftData
When watching the videos it shows examples of how we can read and write to a JSON file as a store, rather than using the built in store that comes with SwiftData.
But there are mentions that we can use cloud storage like a backend i.e. a database hosted on a server. The only thing that I'm struggling to figure out and it would be great if we had code samples for this is how to achieve using cloud storage as a store since looking at the current implementations of:
DataStoreConfiguration
DataStore
The required functions we need to implement look synchronous rather than asynchronous so how would or could we handle fetching asynchronous data from cloud storage. So how would we handle this?
Also it would be great if someone could clarify how or if there is a way to send notifications for changes to your store between different devices similar to CloudKit?
Are there there any plans to provide more documentation & sample code for the questions I've asked above?
Feedback FB13857743
I'm wondering how I can remove the new Writing Tools item from the context menu of a custom view, e.g. using removeMenuForIdentifier: in -buildMenuWithBuilder:.
Ever since the advent of Ventura, saved print settings don’t save detailed selections. Even with Sonoma, almost 2 years later, this issue is still a problem! There is a plethora of Apple Support Community topics to that end:
Print settings don't work any more when upgraded to Ventura
Updated to Ventura—printer presets won’t save
Ventura—Custom Printer Settings not being saved
Printer Not working after Ventura 13.0 update
Problem saving print presets in Ventura
Ventura is not saving printing presets (fully)
Printing Problem with Ventura
macOS Ventura (13.1) print settings don’t save—any resolution?
Printer presets don’t save in Ventura
Print settings are a MESS in Ventura
In the WWDC24 session Evolve your document launch experience, it is mentioned that apps linked against the iOS 17 SDK would not get the new document launch experience. However, I found that the new document browser is active in my iOS 17 app when installed from the App Store on iOS 18, without rebuilding it.
This (along with other iOS 18 UIKit behavioral regressions) renders the app unusable when running under iOS 18. To be clear, my app uses a UIDocumentViewController as the root view controller of a UINavigationController and is implemented primarily in Obj-C.
I don't want to show the new document browser to users at app launch time. The current behavior of my app is that it always launches to either the current document or a new document and then allows the user to open a new document using the document picker if desired (this was accomplished by invoking the action associated with the Documents button on iOS 17; see related feedback FB13418866: ER: UIDocumentViewController should provide API to allow customization of Documents button behavior).
The new UIDocumentViewController behavior is problematic because it has replaced the Documents button with a backAction that moves the user into the new document browser with no way to back out, aside from picking a document or creating a new document. Previously, the user could choose Cancel to exit the document picker and get back to the currently-open document without choosing a new one.
While the new UIDocumentViewController behavior looks nice for apps like Swift Playgrounds, it is problematic for apps that want to take advantage of the UIDocument infrastructure without forcing the user to deal with a more complicated browser-centric app UI.
I would expect there to be some way to maintain the previous behavior as it existed on iOS 17, but I don't see any way to do this. Suggestions welcome. Thanks!
In testing my app with the WWDC24 iOS 18 beta, I have noticed that most of the menu items in the navigation bar and title menu are either missing, disabled, or nonfunctional.
The structure of my app's UI is a UIDocumentController subclass as the root view controller of a UINavigationController.
In debugging the problem with title menu items, I noticed that the responder chain from the UICommand.sender now starts at the UINavigationBar and goes up from there, without passing through the UIDocumentViewController itself. Now, only the actions I've defined in the AppDelegate are accessible.
I'm not exactly sure how this was organized on iOS 17, but the responder chain did include the UIDocumentViewController, where I have implemented most of the menu item actions.
This seems like a UIKit bug, but I am investigating possible workarounds in case Apple does not fix it. Suggestions welcome.
The exact error is: Unable to create bundle at URL (file:///System/Library/CoreServices/SystemVersion.bundle): does not exist or not a directory (0).