We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation .
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Now that the Firebase SDKs are open source, can we then have Carthage support? ??
*** Cloning firebase-ios-sdk *** Checking out firebase-ios-sdk at "4.0.0" *** Skipped building firebase-ios-sdk due to the error: Dependency "firebase-ios-sdk" has no shared framework schemes
The text was updated successfully, but these errors were encountered:
Add Auth Threading Doc ( #9 )
b9cc157
@nidegen I've seen this a few times, but not able to reproduce reliably. I suspect a Carthage race condition since Protobuf.framework is a dependency of multiple components.
Protobuf.framework
Rerunning the carthage update command is a workaround.
carthage update
Sorry, something went wrong.
@paulb777 yes I have also just reupdated carthage a couple of times, but it is really a mess for our CI pipelines????
are the binaries not just download only? how comes carthage has to check out dependencies there?
@nidegen Since Carthage doesn't do dependencies for binaries, the multiple Firebase components that depend on Protobuf.framework need to include it.
Some frameworks are fetching version 5.0.1 and some version 5.1.0.
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json" binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseMessagingBinary.json" binary "https://dl.google.com/dl/firebase/ios/carthage/FirebasePerformanceBinary.json" binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseRemoteConfigBinary.json"
*** Downloading binary-only framework FirebaseAnalyticsBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json" *** Downloading FirebaseAnalyticsBinary.framework binary at "5.0.1" *** Downloading binary-only framework FirebaseMessagingBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseMessagingBinary.json" *** Downloading FirebaseMessagingBinary.framework binary at "5.1.0" *** Downloading binary-only framework FirebasePerformanceBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebasePerformanceBinary.json" *** Downloading FirebasePerformanceBinary.framework binary at "5.0.1" *** Downloading binary-only framework FirebaseRemoteConfigBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseRemoteConfigBinary.json" *** Downloading FirebaseRemoteConfigBinary.framework binary at "5.0.1"
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebasePerformanceBinary.json" == 5.1.0
produces
No available version for binary "https://dl.google.com/dl/firebase/ios/carthage/FirebasePerformanceBinary.json" satisfies the requirement: == 5.1.0
Anyone else seeing this issue?
@paulb777 i dont get it. if binaries have no dependencies (I already understood it that way) why is there an issue with a dependency (protobuf). To me it seems that carthage does check for dependencies after all, or performs some kind of processing of the binaries. i dont see why it should / a binary package is performing anything
@nidegen The Carthage zip files for multiple Firebase components include the Protobuf.framework. If you're using two or more of those components, Carthage will attempt to do multiple copies to ./Carthage/Build/iOS/Protobuf.framework .
./Carthage/Build/iOS/Protobuf.framework
@schlingding Does clearing the Carthage cache make a difference - rm -rf ~/Library/Caches/org.carthage.CarthageKit
rm -rf ~/Library/Caches/org.carthage.CarthageKit
@paulb777 I have tried clearing the cache and removing the Carthage folder as well. Same results. I’m on the latest version of Carthage.
Are you getting 5.1.0 when running Carthage? If so I’ll debug further.
@paulb777 Ran Carthage today and now it's pulling all 5.1.0 versions. Leaving the previous comment intact in case someone else runs into the issue.
5.1.0
Seeing this on "5.2.0"
Failed to write to /.../Carthage/Build/iOS/Protobuf.framework: Error Domain=NSCocoaErrorDomain Code=513 "“Protobuf.framework” couldn’t be removed because you don’t have permission to access it." UserInfo={NSFilePath=/.../Carthage/Build/iOS/Protobuf.framework, NSUserStringVariant=( Remove ), NSUnderlyingError=0x7faa64d60730 {Error Domain=NSPOSIXErrorDomain Code=66 "Directory not empty"}}
Only way to resolve is binary " https://dl.google.com/dl/firebase/ios/carthage/FirebasePerformanceBinary.json " == 5.1.0
@paulb777 For the protobuf checkout bug, deleting cache with rm -rf ~/Library/Caches/org.carthage.CarthageKit actually fixes my issue, probably also yours @walsht
I run it before each carthage update
I also had to manually add SystemConfiguration.framework when I was Carthage-ing Firebase Analytics , otherwise it was complaining about missing a number of SC symbols
SystemConfiguration.framework
SC
Hey guys! Can you add macOS support? The binary binary ".../firebase/ios/carthage/FirebaseAnalyticsBinary.json" is working perfectly for iOS, but it would even greater to have a binary link for macOS as well.
binary binary ".../firebase/ios/carthage/FirebaseAnalyticsBinary.json"
Anyone had troubles updating from 5.4 to 5.6? Missing FirebaseNanoPB and GoogleToolboxForMac , and I'm unable to build the project without those.
FirebaseNanoPB
GoogleToolboxForMac
See #1701 for discussion of carthage update from a release before Firebase 5.5.0 to one after it.
Firebase 5.5.0
Firebase is releasing weeks faster than the updates to the binary files for carthage.
At the time of this post, I'm seeing the latest carthage binary references at 5.8.0 where 5.8.1, 5.9.0, and 5.10.0 have since been released.
Can updating these binary references be part of the Firebase iOS release process or are there further issues?
Please update soon so the community can take advantage of the bug fixes and enhancements.
Thank you!
@schlingding 5.10.0 is now available via Carthage.
See #1862 to follow the status of official Carthage support
Those of you interested in Firebase via Carthage may want to check out Firebase via Rome. Rome provides many of the Carthage features as well as a few additional advantages. Check out the details at https://github.com/firebase/firebase-ios-sdk/blob/master/Rome.md .
We'd love to hear any feedback in another issue .
Closing since Carthage is now available experimentally. We'll track making it officially supported in #1862 .
thanks, @paulb777 clearing carthage cache solved my issue
No branches or pull requests