-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/mobile: building 2 independent xcframeworks for iOS Simulator, but crash when app start up #50594
Comments
@hyangah can you give this a look? |
@pipi32167 are both frameworks built from the same Go package? Does it crash if the two XCFrameworks are built from different Go packages? |
how to solve it? I build 2 xcframeworks also crash |
I just merge 2 xcframeworks into 1. |
I had also same problem. We have 2 independent go library and If I bind two libraries into two different xcframework, It causes a crash.
I used same sys package same dependencies but never succeed. Merging 2 frameworks into 1 is solving problem but I think it needs further investigation |
I had also same problem.
|
If you are using a dynamic link library (go export), this error will not occur. Once the static library is used, this error will be reported. |
Can you provide an example of a dynamic link library? Thank you! |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Building 2 independent xcframeworks for iOS App to use.
And then use the xcframeworks in the Xcode project
What did you expect to see?
The iOS program is able to run properly.
What did you see instead?
The iOS program running crash with the callstack:
The text was updated successfully, but these errors were encountered: