Skip to content
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

Closed
martinmose opened this issue Oct 5, 2023 · 7 comments
Closed

Upload to AppStore - ITMS-90426: Invalid Swift Support #35

martinmose opened this issue Oct 5, 2023 · 7 comments
Labels
app store Occurred when trying to publish to the Apple App Store bug Something isn't working

Comments

@martinmose
Copy link

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:

ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. 
Rebuild your app using the current public (GM) version of Xcode and resubmit it.

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! 🙏

@antoniusnaumann
Copy link
Owner

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.

@antoniusnaumann
Copy link
Owner

Please try the following:

  1. Add "staticlib" to the lib-types in your Cargo.toml.
  2. Try building the Swift package with cargo swift package --release --lib-type static

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).

@antoniusnaumann antoniusnaumann added bug Something isn't working app store Occurred when trying to publish to the Apple App Store labels Oct 5, 2023
@martinmose
Copy link
Author

Thank you for getting back so swiftly, as always 💪.

Using --lib-type static solved the "issue"! 🥳
My apologies, I should've looked into that earlier. It's quite logical now that I think about it.

@antoniusnaumann
Copy link
Owner

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)

@martinmose
Copy link
Author

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. 🙏

@antoniusnaumann
Copy link
Owner

Did you have a successful App Store build so far with dylibs?

@antoniusnaumann
Copy link
Owner

Let's move this discussion to #36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app store Occurred when trying to publish to the Apple App Store bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants