The labels are stored in your mlmodel file. If you open the mlmodel in Xcode 12, it will display what those labels are. My guess is that instead of actual labels, your mlmodel contains "CICAgICAwPmveRIJQWdsYWlzX2lv" and so on. If that is the case, you can make a dictionary in the app that maps "CICAgICAwPmveRIJQWdsYWlzX2lv" and so on to the real labels, or you can replace these labels inside the mlmodel file by editing it using coremltools. (My e-book Core ML Survival Guide has a chapter on how to replace the labels in the model.)

I replied on Stack Overflow, as you asked there too.

Here is a workaround: Open the project in Xcode 11. Go to the auto-generated source file for your model. Copy and paste that into a new Swift source file and add this to your project. Disable source code auto-generation for Core ML models in the project settings. Now open the project in Xcode 12 and it should no longer give that error.

I have had all kinds of weird errors with custom layers in Xcode 12, including the app crashing when trying to load the model. My solution: use coremlc from Xcode 11 to compile the model by hand, add the mlmodelc folder to your project, remove the mlmodel file from the project, and load the model by passing in the URL to the mlmodelc folder in your app bundle. You will also need to copy&paste the auto-generated source file from Xcode 11 into your Xcode 12 project (since you no longer have an mlmodel, it also doesn't generate the source file anymore).

You can use the helper routines from CoreMLHelpers - https://github.com/hollance/CoreMLHelpers. As of iOS 13, Core ML also allows you to pass in CGImage objects but this API is not very straightforward to use. I prefer the method from CoreMLHelpers.

It depends on what features your model uses. If it has a layer type that is only supported by macOS 10.15+, then the model cannot be used on earlier versions of macOS. However, if your model only has the most basic features from Core ML version 1, it can be used on macOS 10.13. There is a field in the mlmodel file named specificationVersion. Set this to 1 to make the model available on 10.13. However, Core ML will give an error if it turns out this model has layer types that are not supported by 10.13. import coremltools as ct spec = ct.utils.load_spec("YourModel.mlmodel")  spec.specificationVersion = 1 ct.utils.save_spec(spec, "YourNewModel.mlmodel")

Since you trained the model to use images as input, you will have to draw the SwiftUI paths into an image first.

Core ML models can only accept RGB or BGR images as inputs (the alpha channel is ignored). If your model wants a YCbCr image, you'll need to put the image into an MLMultiArray instead. You'll also need to change the input of the Core ML model to be a multi-array, not an image. Alternatively, you could add some layers at the start of the model that convert RGB back to YCbCr, but that seems like more trouble than it's worth.

In general, with MLComputeUnitsAll CoreML will try to use the ANE first, but there is no guarantee that it actually will choose the ANE. For more details, see https://github.com/hollance/neural-engine

I don't know what the answer is, but I would try running the model in CPU-only or GPU mode to see if it happens there too. Perhaps it's an issue with the ANE. In any case, these developer forums are pretty deserted. If this is an important issue for your business (and it sounds like it is), you should use one of your Tech Support Incidents or contact a developer evangelist from Apple.

It takes as long as it takes. Using multiple dispatch queues is unlikely to help, since you're limited by how fast the hardware can go. If you want a faster body pose detection method, you will have to train your own model.

Does your model use a NonMaximumSuppression layer (or as part of a pipeline)?