-
Notifications
You must be signed in to change notification settings - Fork 21
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
Upload to AppStore - ITMS-90426: Invalid Swift Support #35
Comments
That's a tough one. I'll look into it, but no idea so far what is causing this. Did you build the Swift package with the --release flag? Currently that's necessary. |
Please try the following:
Ensure that the cargo build commands build a library that ends with .a and not .dylib. (You can see this in the console output of cargo swift). |
Thank you for getting back so swiftly, as always 💪. Using |
I'm glad this solved the issue. (This was just a random guess 😅) Thanks for reporting this, maybe I should deprecate the dylib option entirely (or find out if there is something missing that allows using dylib in App Store) |
I must say I'm partial to the dylib option. Given that I manage three separate repositories (iOS, Android, and Shared code), the ability to check in all necessary files is highly beneficial. Working with .a files poses challenges due to their size, especially when dealing with Git. If we could pinpoint what's preventing the use of dylib in the App Store, that would indeed be invaluable. 🙏 |
Did you have a successful App Store build so far with dylibs? |
Let's move this discussion to #36 |
Hello,
I'm encountering an issue while trying to upload to the AppStore.
Previously, I've successfully uploaded the app even with a shared Rust codebase. The main difference this time is that I'm using
cargo swift
instead of building the.xcframework
myself 📦.After the upload, I received this error:
I've explored various solutions online to no avail. I'm uncertain if this is related to
cargo swift
🤔Any insights or suggestions would be greatly appreciated! 🙏
The text was updated successfully, but these errors were encountered: