I am trying to package a Filemaker 18 Runtime app.
A week ago, I managed to get 90% of the way towards doing as much, using MS Copilot as a guide.
Unfortunately, due to my confusion over the landing stage files, I decided to start the process from scratch.
This time, I fell at the first stage:
Code Signing my .app Bundle.
The Terminal command:
codesign --deep --force --verify --verbose \ --sign "Developer ID Application: ME (V********)" \ "/Users/Me/Documents/Apps/MyApp/Runtime/MyApp/My App.app"
Returned the error:
/Users/Me/Documents/Apps/MyApp/Runtime/MyApp/My App.app: bundle format unrecognized, invalid, or unsuitable In subcomponent: /Users/Me/Documents/Apps/MyApp/Runtime/MyApp/My App.app/Contents/Frameworks/FMWrapper.framework
No matter how many separate elements within the bundle I sign, I encounter the same error message.
A few days ago, the identical command worked first time.
I would be obliged for any help you can provide.
Thanks.
I recommend that you seek help from your third-party vendor here. It seems likely that they’ll have a well-trodden path that you can follow for this.
If you decide to debug this yourself, I have some general hints. To start, dont use --deep when signing code. For an explanation as to why not, see --deep Considered Harmful.
Rather, sign each code item separately, from the inside out. Creating distribution-signed code for macOS explains that process in detail.
I think that’ll reveal that there’s an issue with FMWrapper.framework. If so, that’s good, because gives you something to focus on.
One of the most common causes of weird problems signing frameworks is that folks copy the framework without preserving symlinks. You should check that’s not the case here.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
