After updating to macOS15.2beta, the Yolo11 object detection model exported to coreml outputs incorrect and abnormal bounding boxes.
It also doesn't work in iOS apps built on a 15.2 mac.
The same model worked fine on macOS14.1.
When training a Yolo11 custom model in Python, exporting it to coreml, and testing it in the preview tab of mlpackage on macOS15.2 and Xcode16.0, the above result is obtained.
daisukeMAJIMA
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
I am using NavigationView and NavigationLink in SwiftUI.
And as destinations of NavigationView list, I am setting Views they have UIViewControllerRepresentables .
When I back from UIViewController to top NavigationView lists, UIViewController still stay in memory heap.
And be in trouble, properties in ViewCotroller also is not discard though I set them nil in viewWillDisapper.
How can I discard UIViewControllerRepresentable from memory heap?
Thank you for read this.
struct ContentView: View {
var body: some View {
NavigationView {
VStack {
List {
NavigationLink(
destination: AViewThatHasUIViewControllerRepresentable(),
label: {
Text("AView")
})
NavigationLink(
destination: BViewThatHasUIViewControllerRepresentable(),
label: {
Text("BView")
})
}
}
}
}
}
RealityKit Model Entity will be darker when I use ARWorldTrackingConfiguration. When I place a Model Entity without ARWorldTrackingConfiguration, it is displayed brightly. Why? And does someone know how can I fix it?
May the force be with you and me.
"Provisioning profile failed qualification. \ Profile doesn't include the com.apple.application-identifier entitlement."
When I upload my apps, error message above appear.
Please Help me.