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

iOS - Bundling an app for App Store does not work #9

Open
ArnaudRinquin opened this issue Jan 25, 2018 · 7 comments
Open

iOS - Bundling an app for App Store does not work #9

ArnaudRinquin opened this issue Jan 25, 2018 · 7 comments

Comments

@ArnaudRinquin
Copy link

My build dev and local deployment build using fastlane work just great now but building for the Appstore fails.

screen shot 2018-01-25 at 14 05 19

error: exportArchive: exportOptionsPlist error for key 'method': expected one of {}, but found app-store

Error Domain=IDEFoundationErrorDomain Code=1 "exportOptionsPlist error for key 'method': expected one of {}, but found app-store" UserInfo={NSLocalizedDescription=exportOptionsPlist error for key 'method': expected one of {}, but found app-store}

** EXPORT FAILED **

This issue seems to explain that it comes from external libraries overriding build options. I guess there is something wrong with React-Native-Buglife.

@ArnaudRinquin ArnaudRinquin changed the title iOs - Bundling an app for App Store does not work iOS - Bundling an app for App Store does not work Jan 25, 2018
@schukin
Copy link
Contributor

schukin commented Jan 25, 2018

Hmmm... Buglife isn't overriding any build settings (and AFAIK it's not even possible for Buglife to override your application's build settings the way any workspace is structured that includes it).

Felix himself (author of Fastlane) has used Buglife in personal projects, so this shouldn't be an issue... Investigating now, we might have to submit a PR for fastlane but I'll keep this issue open for book keeping.

@oferRounds
Copy link
Contributor

oferRounds commented Jan 24, 2019

@schukin getting issues as well, when trying to submit to the app store – on my case, from the Xcode organizer. The app icon appears in gray, no version, and the "Upload to App Store" is not available.

I’m still investigating it – not 100% precent sure it’s related to Buglife – but it wasn’t like that on the previous version I uploaded, which the noticeable difference was Buglife integration.

Did you find any solution to this?

@schukin
Copy link
Contributor

schukin commented Jan 25, 2019

@oferRounds could you attach a screenshot? I'm not 100% sure which app icon / upload button you're referring to in Xcode...

@oferRounds
Copy link
Contributor

oferRounds commented Jan 25, 2019

hey @schukin, I actually found the solution. The problem is that the Buglife-iOS project, its Skip Install on its Build Settings is set to No instead of Yes. As a result, the option to distribute the archive as an iOS app is not available, only Build Products (this is relevant when you add a project as sub-project – different than adding it as a pod).

I’m not entirely sure about all this – never encountered it before – but you can see here more on that, and anyhow, doing the above solved it for me:
https://stackoverflow.com/questions/10715211/cannot-generate-ios-app-archive-in-xcode

@schukin
Copy link
Contributor

schukin commented Jan 30, 2019

Hmm, yeah, we've been having on & off issues with React Native, partially due to the pace of change of conventions. Thanks for looking into this, I'll see what we can do on Buglife-iOS to get this resolved here.

@GoMino
Copy link

GoMino commented Feb 1, 2019

Just encountered the exact same problem using react-native-buglife and @oferRounds solutions works !

This fix works in a dev environment because we can manually fix the Buglife.xcodeproj, but in a CI/CD environment, it is not possible without forking the project for now.
Every time we issue the command to install dependencies like npm install or yarn install it will bring back the none working version.

Please push a fix to the npm registry 😇

The following issue fastlane/fastlane#10559 is also mentioning a similar solution.

@GoMino
Copy link

GoMino commented Aug 14, 2019

@gazedash, @schukin can we expect a new release to npm?

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

4 participants