-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/cgo: does not compile for iOS simulator arm64 #57442
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
Comments
iOS simulator on arm64 is not a supported platform yet. You're welcome to file a feature request (or make this issue to), or even better, work on it to make it possible. Thanks. |
Thank you for the quick response. As I do not have any experience implementing such a feature I cannot really help, I will wait for an implementation then. |
I also encountered this problem, and now there is no iphone as a debugging device, the project cannot go on. |
Is there any news about Silicon Simulator support? I was able to create a framework from Go code and I have a weird problem with the Simulator. Sometimes it just hangs on the start and the best that I achieved is that the App runs, but when I get to the point that the Go code is being called, it hangs again, but if I pause from Xcode the code and resume it, it snaps out and it continue. All works ok if I edit the scheme and I disable "Debug executable", but as a developer I think you can imagine that I can't work without debugging. |
Do you have a solution to this problem? |
Nope... |
I would like to add a vote to bump this feature to be added in the dev queue. Development on Mac computers becomes fast an Apple silicone exclusive. |
I found a fix to build with correct (arm64) simulator runtime on Apple Silicon in your
and include the
you can arrive correct |
Hi, this workaround worked for me to be able to create xcframework that does compiles on M1/M2 simulators. But I still have the issue with app handling on app splash screen (probably since my JSI install method happens very early in the app lifecycle and go being called). Gomobile - this project seems to support m1/m2 simulators for a while now (according to their github discussions), but they bind the files for Java/Swift which I'm not interested in (need the native compilation). Can somewhat do the workaround with killing xcode/etc, but would be nive if anyone has suggestion how to fix that. Thx! |
Still hanging on the splashscreen too |
@albertoAround try this. I was facing similar issue for my RN app and this has solved the problem.
Make sure you are setting this only for Debug scheme |
Is there any progress on this, please? arm based macs are the default now pretty much. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
I am using the latest release
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I am trying to compile a go project to iOS c libraries and then create a xcframework out of those libraries.
This works great for iOS arm64 and simulator x86. However, when I try to compile for simulator arm64 I encounter problems.
The library built for arm64 simulator seems to not target the simulator but a real iOS device. This is problematic for using the simulator on new apple silicone devices.
I compiled using this command
and this is the
clangwrap.sh
When now creating a xcframework
the error is
What did you expect to see?
I expected the library to be built for an arm64 simulator.
What did you see instead?
The library was built for an arm64 iOS device.
The text was updated successfully, but these errors were encountered: