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

Command PhaseScriptExecution failed with a nonzero exit code #817

Closed venkataraja705 closed 1 year ago

venkataraja705 commented 1 year ago

Versions

Describe the bug when i try to build the project i was getting error message as -> Command PhaseScriptExecution failed with a nonzero exit code

To Reproduce i created new virtual environment using venv python installed kivy ios using : pip install kivy-ios create a reciped using toolchain : toolchain build python3 kivy openssl create project : toolchain create [app name] [folder source to files] i was getting and error

i tried my code with kivy android and tested in the real android mobile and it is working fine. but i am trying in the kivy-ios i was getting error

Expected behavior // REPLACE ME: A clear and concise description of what you expected to happen.

Logs

// REPLACE ME: Paste the build output containing the error
i uploaded my logs here

[Build atestapp_2023-06-11T20-33-07.txt](https://github.com/kivy/kivy-ios/files/11717393/Build.atestapp_2023-06-11T20-33-07.txt)

Screenshots

Additional context Add any other context about the problem here. i uploded my logs in the context please refer to that

venkataraja705 commented 1 year ago

Build atestapp_2023-06-11T20-33-07.txt

misl6 commented 1 year ago

Hi @venkataraja705 !

You need to exclude folders that are not supposed to be inside your iOS artifact, such as dist.

Closing as support, feel free to join our support channels and ask for help! 😀

github-actions[bot] commented 1 year 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.