-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ios support #61
Ios support #61
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like it almost worked for me. After installing Xcode, the iPhone simulator, and the required toolchains, a make run
inside the mobile/
directory manages to build, but then dies trying to launch a simulator.
[snip]
/usr/bin/touch -c /Users/nathan/rust/bevy_game_template/mobile/build/Build/Products/Debug-iphoneos/mobile.app
** BUILD SUCCEEDED **
xcrun simctl boot 3rd || true
Invalid device or device pair: 3rd
xcrun simctl install 3rd build/Build/Products/Debug-iphonesimulator/mobile.app
Invalid device: 3rd
make: *** [install] Error 148
I pushed the WIP manifest.yaml to switch from
|
Co-authored-by: Nathan Stocks <[email protected]>
I'm happy to test for iOS again once you have it working for yourself. |
I now see everything in my simulator. Apparently iOS requires I've also been working on extending the release flow for android and iOS builds. Since I don't have access to an iPhone at the moment, maybe someone could check a build for me?
|
I should be able to test this later today. |
I was able to "install" both .ipa files by dragging them onto my iPhone's finder window, but trying to run them failed with the same error for both:
I'm not super surprised -- because I don't know of any ad-hoc way of installing someone else's app without at least signing it with your own development certificate. Or going through the app store with testflight or an official release. But then, I am no iOS expert, maybe I just don't know what I'm supposed to do to make it work. I am able to do
† As long as I keep adding in my Makefile patch that I suggested to fix the device id scraping |
Thank you for testing again. I would have thought that there is a way to trust an unsigned app and install it anyways. |
…uild to export it
After a lot of trial and error, the new workflow to prepare and upload an ipa to app store connect finally works 🥳 . A friend of mine has verified via TestFlight that the build runs fine (although it doesn't seem to have any audio, but that a separate issue I guess). |
I forgot to mention in my last comment that audio had stopped working.
Unfortunately, I still get the same error. 😕 |
# Objective - Make sure that users can "just run" the mobile example - Device descriptions like `iPhone SE (3rd generation) (F647334F-D7C1-4BD6-9B5F-0E3D9713C02B) (Shutdown)` currently fail ([issue found](NiklasEi/bevy_game_template#61 (comment)) by @CleanCut) ## Solution - Improve the script that grabs the device UUID from the device list
# Objective - Make sure that users can "just run" the mobile example - Device descriptions like `iPhone SE (3rd generation) (F647334F-D7C1-4BD6-9B5F-0E3D9713C02B) (Shutdown)` currently fail ([issue found](NiklasEi/bevy_game_template#61 (comment)) by @CleanCut) ## Solution - Improve the script that grabs the device UUID from the device list
# Objective - Make sure that users can "just run" the mobile example - Device descriptions like `iPhone SE (3rd generation) (F647334F-D7C1-4BD6-9B5F-0E3D9713C02B) (Shutdown)` currently fail ([issue found](NiklasEi/bevy_game_template#61 (comment)) by @CleanCut) ## Solution - Improve the script that grabs the device UUID from the device list
# Objective - Make sure that users can "just run" the mobile example - Device descriptions like `iPhone SE (3rd generation) (F647334F-D7C1-4BD6-9B5F-0E3D9713C02B) (Shutdown)` currently fail ([issue found](NiklasEi/bevy_game_template#61 (comment)) by @CleanCut) ## Solution - Improve the script that grabs the device UUID from the device list
Resolves #30