kivy / kivy-ios

Toolchain for compiling Python / Kivy / other libraries for iOS
https://kivy.org/docs/guide/packaging-ios.html
MIT License
758 stars 238 forks source link

Invalid Signature when adding Python to iOS App Extension #826

Closed chaitanyapandit closed 8 months ago

chaitanyapandit commented 11 months ago

Versions

Describe the bug I need to execute Python code in my iOS app as well as the a Share extension of the app. Everything works when running via Xcode, but when I try to submit to the App Store, it fails with error:

Asset validation failed Invalid Signature. Code object is not signed at all. The file at path “MyApp.app/PlugIns/MyAppShare.appex/lib/python3.10/site-packages/urllib3/util/timeout.py” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. (ID: xxxx-xxxx-xxxx-xxxx-xxxx) ....

Looks like it is complaining about the .py files inside the share extension bundle (PlugIns > MyAppShare.appex > lib > python3.10 Attached screenshot for directory structure)

To Reproduce

Expected behavior

Logs

Screenshots

share-dir

Additional context

github-actions[bot] commented 8 months ago

👋 We use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. Please use our support channels to get help with the project.

If you're having trouble installing or using kivy-ios, maybe you could be interested to installation and requirements.

Let us know if this comment was made in error, and we'll be happy to reopen the issue.