-
-
Notifications
You must be signed in to change notification settings - Fork 382
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
Documentation is unclear that physical iOS devices aren't yet supported #1190
Comments
Crosslinking; may still be room for doc improvements, though: |
Ah. Yea ok. Didn't find that when searching. Yea, the docs should definitely change! As of now they lie, and don't mention this workaround which is what you actually need. |
Although. Now that I've tried to open xcode with from . import _bcrypt # noqa: I100 at least it finds the so file! :P |
After debugging help for #1189, I got that to work by
There's clearly something fishy about the build folder! That the xcode project is IN the build folder seems less than ideal if I have to nuke it periodically. Maybe there should be Anyway, I tried nuking |
@boxed I am also facing same issue. My custom framework is working fine in simulator. But not working in real device. Below is my error. Any workaround or fixes you had for your issue ?
|
Briefcase does not yet support running apps on a physical iOS device. There's a workaround in #860, but if you want to add custom frameworks then that's probably out of Briefcase's scope, and you should seek help in a more general iOS forum. Let's keep this issue focused on improving the documentation. |
We need to be clear that there's 2 issues being discussed here. The first is starting apps on iOS devices from the Briefcase command line. This is a gap in documentation. The second is adding external frameworks to your iOS app. I'd argue it is in scope for Briefcase - it's the manifestation of #485 on iOS/macOS, which is being addressed on Android by #1610 - but it is completely distinct from the subject of this ticket (launching on iOS devices). |
Describe the bug
I failed to test my app in the simulator (see #1189) so I tried running on device. I failed with this too and noticed the docs are... a bit weird.
Steps to reproduce
Ran
briefcase run iOS -u -r -d <my UDID as copy pasted from XCodes devices list>
Get the error message
Invalid device device name '<UDID>'
Expected behavior
App installed and started on phone.
Screenshots
No response
Environment
Logs
No response
Additional context
I read through the code and it does look rather suspicious. It looks like it validates the device IDs against a list it gets from a function call
get_simulators
. But I'm not trying to run on a simulator, I'm trying to run on a real device...The docs at https://docs.beeware.org/en/latest/tutorial/tutorial-5/iOS.html are rather weird about this. They show how to get something running on a simulator, but then at the end say "We’ve now got an application on our phone!". Which isn't what the commands above is doing or the text above talks about.
When I run just
briefcase run iOS
it shows a menu asking which simulator... but I don't want a simulator. I want the real phone.The text was updated successfully, but these errors were encountered: