Xcode 12 release compiling failed

[beiguancyc]

Using Xcode 12 release compiling for an iOS Simulator running iOS 14, the app cannot compile when the Parse pod is installed.

Repro steps
pod 'Parse','~> 1.19.0'
Then build and run,

[idefen1]

Got it.

Switch '@import Bolts' to '#import <Bolts/Bolts.h>' and my project compiled.

Hope this helps.

[beiguancyc]

Got it.

Switch '@import Bolts' to '#import <Bolts/Bolts.h>' and my project compiled.

Hope this helps.

That is not a good idea

[idefen1]

Got it.
Switch '@import Bolts' to '#import <Bolts/Bolts.h>' and my project compiled.
Hope this helps.

That is not a good idea

I'm sorry =\ I don't know what else to do... I need to compile my code and this is the only way I can get it to work. Maybe someone else will help us find a fix.

[beiguancyc]

Got it.
Switch '@import Bolts' to '#import <Bolts/Bolts.h>' and my project compiled.
Hope this helps.

That is not a good idea

I'm sorry =\ I don't know what else to do... I need to compile my code and this is the only way I can get it to work. Maybe someone else will help us find a fix.

I think it will be fixed soon.

[idefen1]

Got it.
Switch '@import Bolts' to '#import <Bolts/Bolts.h>' and my project compiled.
Hope this helps.

That is not a good idea

I'm sorry =\ I don't know what else to do... I need to compile my code and this is the only way I can get it to work. Maybe someone else will help us find a fix.

I think it will be fixed soon.

Just a quick question: Why is my quick fix 'not a good idea'. My application appears to be compiling and working as expected? If I need to submit, what risk am I taking? Thanks!

[gutoim]

I think this is the fix. The build error occurs when building pod (including Parse) into a static library. Using @import Bolts requires using use_frameworks! in Podfile, which for sure I do not want.

[theextremeprogrammer]

Just a quick question: Why is my quick fix 'not a good idea'. My application appears to be compiling and working as expected? If I need to submit, what risk am I taking? Thanks!

@idefen1 Based on my understanding of how Cocoapods works, if you change this line of code then anytime you update or refresh your pods then this change will be deleted. So while this may work for right now as a temporary solution, ideally the long term solution would be to have this change (or the appropriate change) made to the Parse SDK itself so that you (and me and others) don't have to continue to manually make this fix in the future.

[findlife99]

Hi,

I also face the same problem, how can I solve it ?

[theextremeprogrammer]

Hi,

I also face the same problem, how can I solve it ?

@findlife99 The fix mentioned in this comment worked for me - however, as I noted above, making a change to the pod source code should be considered temporary, so I made a PR to be considered for inclusion in a future build.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. If you believe it should stay open, please let us know! As always, we encourage contributions, check out the Contributing Guide

[theextremeprogrammer]

Doesn't look like I have the ability to close this issue, but since the PR was merged I think was can close this. @TomWFox @drdaz could I trouble you to assist? Thanks! =)