-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Enable Client build for iOS simulator #1252
Comments
FYI, here is an attempt to generate the tun2socks xcframework: Jigsaw-Code/outline-go-tun2socks#85 To be validated. |
Note that the iOS simulator does not support the NetworkExtension framework used to establish the VPN. A simulator build may be useful to test UI, but you may need to mock out the NE VPN functionality. |
It turns out Sentry 4 only supports arm64 for iOS: Sentry needs to be upgraded to version 5+. |
After updating Sentry and Tun2Socks, I was able to run on the simulator. However, I can't connect: On the logs, I see:
|
@alalamav any idea how I can grant the VPN permission to the app? |
This is done. We can now build for the simulator, even though the VPN doesn't work. These commands now work after you created and prepared the ios platform with
@daniellacosse I believe we will need to tweak the build scripts to allow for building for the simulator. With the cordova CLI we could call |
Currently our client doesn't run on the simulator because our dependencies are built for the device architecture.
We should migrate the dependencies to xcframeworks. Both Carthage and go-mobile already support that.
We will probably need to edit the xcode project.
after_prepare
hookThose dependencies are specified in the plugin.xml. We will need to update that file to refer to the xcframework files
We may need to also edit the xcode project because I think we disable some architectures.
We may be able to migrate the Carthage dependencies to cocoapods, at least on ios, since Cordova seems to support it (see spec). Though it may be better to have a more unified architecture with macos and just use a xcframework (or migrate macOS to Cocoa pods somehow)
/cc @daniellacosse
The text was updated successfully, but these errors were encountered: