Kivy-ios 'hello world' fails to build to simulator on new M2 Mac mini with MacOS 14.4.1 and XCode 15.3 #35
Replies: 6 comments 1 reply
-
Well, I am a little ahead of you on Xcode 15.4 and macOS 14.5. I am getting a little further in my build process but fail after about 29 seconds with a "rsync warning: some files vanished before they could be transferred (code 24)" error code. Platform build and xcode project creation steps seem to have occured correctly. Seems to me this was working last week, but I've reset my macOS and re-installed fresh since to try and isolate the issue. Note that I am developing on a Mac mini M1 device. Good to know I am not alone... |
Beta Was this translation helpful? Give feedback.
-
yeah XCode 15 has different build mechanism from previous releases. I am unable to produce IPA that would be able to publish in the store. Emulator build works but then application crashes (see issues it is a known problem) still the same application runs on a physical device. Not being able to store publish is a biggest PITA :-( |
Beta Was this translation helpful? Give feedback.
-
I have confirmed that upgrading to XCode 15.4 does not change the build issue. My hello world program fails to build with the same linker errors. I will try it again when either XCode or kivy-ios gets another update. |
Beta Was this translation helpful? Give feedback.
-
Probably some build dependencies / packages / tools / recipes are missing (target python recipe?). Try using buildozer:
Notes:
|
Beta Was this translation helpful? Give feedback.
-
Buildozer on Apple is more broken than kivy-ios I am afraid. You are the first person who suggested I use it as most people recommend avoiding it. I have been using Buildozer on Android for the last 8 months successful, the iOS logic needs some TLC however. I tried again after upgrading to OSX 14.7 with the same results. I didn't expect any changes. I am hesitant to upgrade to OSX 15 and XCode 16 as I am afraid the tools will just get further and further away from a compatible software combination. I will try again in a month or two and see if the lie of the land has changed in the iOS Kivy camp. |
Beta Was this translation helpful? Give feedback.
-
Hello! I am also unable to build my app on Xcode. I get "Command PhaseScriptExecution failed with a nonzero exit code". Xcode 15.2, MacMini M1. Any Ideas? Is the iOS-Kivy-thing still supported and updated? I mean am I trying something that should normally work? Thanks! |
Beta Was this translation helpful? Give feedback.
-
I created a 'hello world' app to test kivy-ios on a new mac mini and have been unable to get it to build in XCode. I fear I may have a "too new" problem where kivy-ios is not compatible with this new dev environment.
I followed the instructions on https://github.com/kivy/kivy-ios and have reached the "click Play" in XCode to start the simulator and get a unresolved symbols build failure.
The hello world program is very simple.
main.py:
main.kv:
When I run XCode as so:
$ open helloworld-ios/helloworld.xcodeproj/
I get this error:
What I know is that main.o is being linked to libSDL2.a to resolve they symbol for SDL_main but the linker is failing to link libpython3.11.a into the build to resolve the symbols in libSDL2.a. I have been unable to figure out how to get XCode to perform the correct link.
I am thinking this is a regression issue, otherwise I would expect other people to be reporting this issue. But I cannot confirm this as I do not have access to older MacOS environments.
Anyone have any suggestions? I would be more than happy to assist in helping get kivy-ios working for MacOS 14/XCode 15.3.
Beta Was this translation helpful? Give feedback.
All reactions