Encrypted CoreML model load fails with vague error

Question

Created Jun ’21

Replies 4

Boosts 0

Views 2.8k

Participants 5

Xcode Version: 12.4 (Used Xcode 12.5 to create encryption key as 12.4 is bugged and will not let you)

I am bundling a ML model into my app, and have encrypted ML model via Xcode 12 encryption method shown here. Model loads and works fine without encryption. After adding model encryption key and setting it as compiler flag, the model encryption/decryption works fine in a demo app, but using the same load method in my main app fails with this error message:

Thread 1: Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=com.apple.CoreML Code=0 "Unable to load model at /path_to_model/my_model.mlmodelc/ with error: failed to invoke mremap_encrypted with result = -1, error = 12"

I have tried all variations of the load method available within my swift generated model file, all produce the same result above.

Boost

Answer 1

OP

Apple

Jun ’21

Hi, what is the difference between the demo app and the main app in this case? Could you please check if the main app is code signed?

0

Answer 2

justadev1 OP

Jun ’21

Do you by any chance bundle the model directly in your demo app, but bundle it into a separate framework in your main app?

We have the same error specifically when we place our encrypted models into a framework bundle and let the framework load them. The problem appeared in iOS 14.5 and is currently present in 14.6 as well. If we move the models out from the framework bundle, and let the framework load them from the app bundle, it works fine. Everything also works with non-encrypted models.

I've checked our app, and the framework is set to "Embed & Sign" in the project settings. OurFramework.framework/_CodeSignature/CodeResources file seems to be generated correctly too. Yet we still get the error.

1

Answer 3

efabianappledev OP

Jul ’21

I'm facing the same issue. When the model is bundled in a framework it fails to load. Any help is appreciated!

0

Answer 4

imxieyi OP

Oct ’21

I had the same issue with a model in a .bundle folder. I found a workaround for it. It should also work for frameworks.

Instead of using

Bundle(identifier: "com.company.bundle").url(forResource: "model", withExtension: "mlmodelc")

you can use

Bundle.main.url(forResource: "model", withExtension: "mlmodelc", subdirectory: "bundle.bundle")

This is definitely hacky but it works in my case.

0