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

Invalid Swift Support error occurs when deploying App to the Appstore #39

Closed
IjzerenHein opened this issue Sep 25, 2016 · 11 comments
Closed
Assignees
Labels

Comments

@IjzerenHein
Copy link

IjzerenHein commented Sep 25, 2016

Hi,

I've reached the point where I am deploying the App to the iOS app-store, but the app is being rejected because of the following error:

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

After some investigating and disabling libraries I found that this happens when including firestack. After removing firestack using react-native unlink react-native-firestack the problem disappears.

Has anyone already ran into this, any solutions?

thanks,
Hein

@tarkanlar
Copy link

Hi I haven't deploy yet but when I tried to integrate https://github.com/fullstackreact/react-native-oauth I have seen the same error and removed oauth

@auser
Copy link
Contributor

auser commented Sep 26, 2016

Yes, the auth library requires swift... I think I need to update the README as I haven't touched react-native-oauth in a little bit.

@auser auser closed this as completed Sep 26, 2016
@IjzerenHein
Copy link
Author

Why has this been closed? I'm not using oauth in any way in my app, nevertheless the deploy to the app store is failing.
Should I change something in my app to resolve this?!

@auser
Copy link
Contributor

auser commented Sep 26, 2016

What is the error, @ljzerenHein? Is it still giving you the same trouble without react-native-oauth?

My bad, I thought you said it went away after removing the OAuth library.

@auser auser reopened this Sep 26, 2016
@IjzerenHein
Copy link
Author

Yes, I'm not using react-native-oauth. I merely included react-native-firestack in my app and am only using the Storage functionality of that.

@auser
Copy link
Contributor

auser commented Sep 26, 2016

@ljzerenHein. Okay, lemme check it here.

@IjzerenHein
Copy link
Author

Awesome, thanks @auser

auser added a commit that referenced this issue Sep 26, 2016
@auser
Copy link
Contributor

auser commented Sep 26, 2016

Update: I'm able to replicate this. Hunting it down now.

@danvass
Copy link
Contributor

danvass commented Sep 27, 2016

Can confirm I received the same issue. Glad to see it being resolved!

@auser
Copy link
Contributor

auser commented Sep 30, 2016

I resolved this the simplest way...

I have not pushed the update to npm yet (I want to make sure it works for everyone and update the README). Please, update your libraries and run this command:

rnpm unlink react-native-firestack && react-native link react-native-firestack

It will create a Podfile for you and install the dependencies, if you don't already have one.

@auser auser added the bug label Sep 30, 2016
@auser auser self-assigned this Sep 30, 2016
@IjzerenHein
Copy link
Author

Alright cool, I'll hopefully get around testing this soon. I'll keep you posted

@auser auser closed this as completed Oct 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants