Skip to content
This repository has been archived by the owner on Jan 13, 2023. It is now read-only.

[Swift] Could not build modules during Archiving and "Include of non-modular header inside framework module RxLibrary" #30

Closed
damienromito opened this issue Dec 15, 2016 · 10 comments

Comments

@damienromito
Copy link

When I wanted to archive my app to build a Testflight app on itunes connect, I get several errors. Then I try with the demo project "Speech" and I get the same errors:

screen shot 2016-12-15 at 16 28 41

I found this post on the first issue, but I couldn't manage.

@damienromito damienromito changed the title Archiving failed with the Swift project Archiving failed with the Swift project "Include of non-modular header inside framework module .." Dec 15, 2016
@damienromito damienromito changed the title Archiving failed with the Swift project "Include of non-modular header inside framework module .." [Swift] Could not build modules during Archiving and "Include of non-modular header inside framework module .." Dec 15, 2016
@damienromito damienromito changed the title [Swift] Could not build modules during Archiving and "Include of non-modular header inside framework module .." [Swift] Could not build modules during Archiving and "Include of non-modular header inside framework module RxLibrary" Dec 15, 2016
@damienromito
Copy link
Author

I managed to archive the app just by commenting the line.This create a warning but the voice detection works well.

screen shot 2016-12-16 at 14 10 24

@tsuyoshiishikawa
Copy link

I resolved!

@damienromito
Copy link
Author

damienromito commented May 23, 2017

@tsuyoshiishikawa How?

@tsuyoshiishikawa
Copy link

I only commented out.
2017-05-23 21 28 20

@damienromito
Copy link
Author

@AppHero2
Copy link

AppHero2 commented Jun 5, 2018

Firebase Firestore could not build modules while archiving app, but I can archive if I comment the above line (#import "transformations/gRXMappingWriter.h")

@jacobokoenig
Copy link

Will this be fixed in any upcoming updates soon? Every time I install a new dependency I need to go back and comment this line before archiving.

@ramsalazar
Copy link

@jacobo360 As of now this issue has been fixed already on the 1.13.0 version release on gRPC. I just did it on my project and update the pod file to grab the updated version because the previous version I had is 1.12.0

@jacobokoenig
Copy link

Brilliant. Thanks!

@iamatulkumar
Copy link

I figured out the problem, all of the deployment targets need to be the same. That is, in the project file, the target, and the pods project as well.

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

No branches or pull requests

6 participants