x/mobile: `gomobile bind` produces xcframework incompatible with new Xcode 15.3 requirements for iOS builds

[scosman]

Go version

go1.22.0 darwin/arm64

What did you do?

gomobile bind to produce a xcframework

What did you see happen?

The output xcframework isn't compatible with Xcode 15.3 (new Xcode release), when used with iOS devices.

It works on simulator now because of a fix I made for: #66018

However the following tasks fail:

• Debugging on a real device
• Validating an app archive containing the xcframework
• Releasing an app using the xcframework

I've determined the fix, described here: #66018 (comment)

I believe the fix is to follow the Apple "placing content in a bundle" docs fully. Previously we follow the MacOS docs, then create symlinks from where content is expected on iOS to the MacOS locations. To fix we should follow the right format per platform, without symlinks. We also need to add the new keys.

Open to other suggestions on how to fix. Will try to make a patch next week using approach above if no other suggestions are made.

cc @hajimehoshi @Simon-Zeng

What did you expect to see?

It should work on Xcode 15.3 😀

[hajimehoshi]

CC @hyangah @dmitshur

[scosman]

WIP fix: https://github.com/scosman/gomobile/commits/master/

[gopherbot]

Change https://go.dev/cl/574055 mentions this issue: cmd/gomobile: produce frameworks which follow Apple's specs per platform, fixing Xcode 15.3 compatibility issues

[Simon-Zeng]

@scosman This fix should take Mac OS compatibility into consideration too, as reported in #66406 .

[Simon-Zeng]

@scosman For symlinks, There seems to be a mistake using "A": "Versions/Current". Shouldn't it be "Versions/A": "Versions/Current"?

[scosman]

@Simon-Zeng added a comment explaining that above. dst is relative to src. If both are absolute, when the framework is copied, it keeps original path. This keeps it all relative. Result is correct: Current -> A