HomeiOS Developmentios - The next Swift pods can not but be built-in as...

ios – The next Swift pods can not but be built-in as static libraries:


I’m making an attempt to deploy my first expo challenge to the apple App Retailer however I preserve getting a construct error whereas constructing my app with the EAS server. Beneath is the detailed log report

[!] The next Swift pods can not but be built-in as static libraries:
96
The Swift pod `FirebaseCoreInternal` relies upon upon `GoogleUtilities`, which doesn't  
outline modules. To decide into these targets producing module maps (which is critical to 
import them from Swift when constructing as static libraries), chances are you'll set 
`use_modular_headers!` globally in your Podfile, or specify `:modular_headers => 
true` for explicit dependencies.
97
The Swift pod `FirebaseStorage` relies upon upon 
`FirebaseAppCheckInterop`,`FirebaseAuthInterop`, `FirebaseCore`, 
`FirebaseCoreExtension`, and `GTMSessionFetcher`, which don't outline modules. To 
decide into these targets producing module maps (which is critical to import them 
from Swift when constructing as static libraries), chances are you'll set `use_modular_headers!` 
globally in your Podfile, or specify `:modular_headers => true` for explicit dependencies.

in keeping with this log I believe it requires me so as to add some config to my pod file however since I am utilizing expo managed I’ve to pod file.

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments