-
Notifications
You must be signed in to change notification settings - Fork 15
Validating for the Mac App Store #3
Comments
Hm, that's a head scratcher. According to the docs:
I pulled down the framework as-is from jcenter and verified that the CFBundleExecutable key was libtesseract. Could you check the value of the Info.plist in the framework embedded in your App bundle and let me know what it says? |
Also, could you make a minimal repo that has the same project configuration as you're working with so I can reproduce the issue on my end? |
Not sure if this could also potentially be the issue, but there was a person who opened an issue on the main SwiftyTesseract repo having issues related to code signing SwiftyTesseract/SwiftyTesseract#75. Apparently Xcode 12 has an issue where it is not code signing Swift Packages |
The problem here I think is that Xcode embeds libtesseract.framework into the app package. I've temporarily solved this by adding a Run Script phase at the end of Build Phases for removing the framework from the package:
This also solves the other issue (SwiftyTesseract/SwiftyTesseract#75) related to missing code signature, since the binary won't be there unsigned. |
Hello, |
Hello,
Great framework you developed here. But I have a problem. When I try to validate an app with this embedded framework I receive an error when uploading/validating:
App Store Connect Operation Error
Bad Bundle Executable. You must include a valid CFBundleExecutable key in the nested bundle libtesseract [com.testapp.pkg/Payload/TestApp.app/Contents/Frameworks/libtesseract.framework] property list file.
Any idea?
The text was updated successfully, but these errors were encountered: