Why not ship the binaries with the pub packages? See #4698 for a full example of integrating with automatic versioning based on what firebase_core uses. No changes to the FlutterFire packages were required. target 'Runner' do pod 'FirebaseFirestore', :git => '', :tag => '7.4.0' #. To integrate, you just need to add 1 line to your ios/Podfile inside your Flutter project To help you consume these quicker with the least amount of changes to your codebase we've created invertase/firestore-ios-sdk-frameworks - a repository that provides a drop in replacement podspec for Firestore that consumes the precompiled binaries instead, without you needing to download 3gb of SDKs and manually extract out the Firestore SDKs from the rest of the SDKs in the zip. The way to do that would be to consume precompiled binaries, in the new XCFramework bundle type introduced to Xcode last year, luckily as part of the Firebase iOS SDK release process these bundles are generated and published in a zip containing all Firebase SDKs. The biggest win to improving build times would be to not have to compile all that C++ code. Currently the Firestore iOS SDK depends on some 500k lines of mostly C++ code (from dependencies such as gRPC), which when compiling as part of your Xcode build can take a long time - even more so in CI environments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |