3

Using Swift-Package-Manager, Swift5.3.2, iOS14.4.1, XCode12.4,

I am trying to integrate Firebase into my iOS App.

I use the Swift Package Manager for Firebase (Beta) as described here.

After successfully integrating most packages from the Firebase selection choice (since I need most of them), I get the following error in Xcode:

'openssl/arm_arch.h' file not found

It seems to happen in the File crypto.c of the BoringSSL dependency added by the Firebase dependency. (see screenshot)

enter image description here

I know the problem has be described before (such as here, here, here and here). However, most of the people use Cocoapods. But in my case, I use the Swift Package Manager. So I open up this question again:

What do I need to do when Xcode said 'openssl/arm_arch.h' file not found ?

Jan Hernandez
  • 4,414
  • 2
  • 12
  • 18
iKK
  • 6,394
  • 10
  • 58
  • 131
  • Same issue here, seems like somethings gone wrong very recently... – smörkex Mar 24 '21 at 19:09
  • 2
    Well, it turns out that time heals all wounds and [now that BoringSSL-GRPC 0.0.9 has magically appeared](https://github.com/firebase/boringSSL-SwiftPM/tags), my error went away. So just update to the latest packages and stay away from `0.0.8`... – smörkex Mar 24 '21 at 20:31
  • uff yes, seems that Google made some extra loop here with the Firebase deployment for Swift Package Manager. – iKK Mar 24 '21 at 21:03

1 Answers1

1

Yes, as is referenced in the comments, 7.9.0 was initially a bad release for the Firebase Swift Package Manager distribution. It was fixed and the 7.9.0 repo tag updated but Xcode/SPM caching prevented the new tag from being honored for people rerunning, so we made an equivalent 7.9.1 release to definitively fix the issue.

Full details at https://github.com/firebase/firebase-ios-sdk/issues/7777

Paul Beusterien
  • 27,542
  • 6
  • 83
  • 139