Xcode 12.4 Build getting failed

[thebergamo]

Xcode 12.4 Build getting failed

[jamesxabregas]

Just came across this same issue. Added an empty swift file to create the bridging header in my project and it fixed the issue as described here. I was able to delete the empty swift file afterwards.

[claudiozam]

@jamesxabregas thanks for your help! It is working!!

I'm using XCode 12.5 + RN 0.63.4

[mikehardy]

Have you tried using Xcode 12.5 + react-native 0.63.3 ?
(I'm using 12.5 + 0.64.1 and it's working fine, Xcode 12.5 and 0.63.3 are compatible as well)

[aamir-ans]

@mikehardy No I didn't, currently I don't have any plan to upgrade react native version. Is there anyway to handle this using react native version 0.62 and Xcode 12.4 ?

[mikehardy]

No idea, I only use react-native versions that still compile with current stable versions of Xcode (12.5), sorry

[thebergamo]

@aamir-ans maybe you can try this: facebook/react-native#29633 (comment)

[mikehardy]

I think it's possible to say this module does not have a compile issue at this point, so no need to keep it open. I just built it myself in my project and it's fine as far as I can tell at least, along with success reports above. Cheers

[jamesxabregas]

I think it's possible to say this module does not have a compile issue at this point, so no need to keep it open. I just built it myself in my project and it's fine as far as I can tell at least, along with success reports above. Cheers

Perhaps this cavet should be added to the readme?

[mikehardy]

@jamesxabregas - that is a great idea, I happened to have the bridging header from long ago so it did not bite me but it is a pretty esoteric error. Hit the edit button on the README and if it looks reasonable at all I'll happily 👍 it to save future devs from pulling hair out

[jamesxabregas]

@jamesxabregas - that is a great idea, I happened to have the bridging header from long ago so it did not bite me but it is a pretty esoteric error. Hit the edit button on the README and if it looks reasonable at all I'll happily 👍 it to save future devs from pulling hair out

Looks there was already a refrence to it in the Torubleshooting section but it only mentioned the solution and not the problem, so it was hard to understand. Pushed through the changes to the readme to make it clearer.