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

Problems on publishing app using Xamarin.Swift3 support from Apple (CI/CD pipeline) #16

Closed
stvansolano opened this issue May 11, 2018 · 2 comments

Comments

@stvansolano
Copy link

stvansolano commented May 11, 2018

Hello @Flash3001 have you guys tried publishing apps with Xamarin.Swift3 packages? I tried recently with a binding library that depends on Xamarin.Swift3.Support but unfortunately it doesn't get processed by Apple correctly.

Is there a workaround that you guys would recommend for making ipa-packager process for CI/CD pipelines? Here is the text I get from Apple team in case anyone takes the same.

Dear Developer,

We identified one or more issues with a recent delivery for your app. Please correct the following issues, then upload again.

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

Best regards,

The App Store Team

After removing the binding and the Xamarin.Swift3 references it gets processed. I saw some workarounds on copying the missing folders but didn't like doing that or block CI/CD scenarios

@stvansolano stvansolano changed the title Problems on publishing app using Xamairn.Swift3 support from Apple Problems on publishing app using Xamarin.Swift3 support from Apple May 11, 2018
@stvansolano
Copy link
Author

Moving to use IPA packager for solving that.

https://github.com/Flash3001/ipa-packager

A way to have that as CI/CD for IPAs would be helpful :)

@stvansolano stvansolano changed the title Problems on publishing app using Xamarin.Swift3 support from Apple Problems on publishing app using Xamarin.Swift3 support from Apple (CI/CD pipeline) May 12, 2018
@Flash3001
Copy link
Owner

Hey @stvansolano

I'm not sure I understood the issue.

We make it work in our CI by adding a call to the ipa-packager script as a new step right after the compilation process. So as soon as we get the IPA we run the script and get a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants