Closed agirault closed 4 years ago
I found a few problems with this issue:
Also, I'm curious why run
and upload-symbols
are in the FirebaseCrashlytics-*.zip
file referenced by FirebaseCrashlyticsBinary.json
along with the framework, but they are not present when letting Carthage
grab them.
@agirault Thanks for the report. I'm able to successfully carthage update
to the 6.29.0 versions, so not able to reproduce.
For the second question, it's a result of Carthage being opinionated about only installing frameworks and nothing else.
Since you have a workaround and it's not obviously reproducible, I'll mark this needs-info
to auto close unless we get other reports or additional information.
I just had a collaborator try it out without any issue on his end, just like you. I'm using the latest carthage
so this is surprising. Thanks for the follow-up, good to let auto close.
I see my comment removed the needs-info
tag so I'll simply close the issue. Thank you.
Step 1: Describe your environment
Carthage
(0.35.0)Step 2: Describe the problem
Trying to use Carthage to install Firebase Analytics, Crashlytics, Performance, and Protobuf (required by Performance) resolves to different versions of Firebase (mix of
6.28.1
and6.29.0
) which isn't recommended, even though the*Binary.json
files all have entries for6.29.0
Steps to reproduce:
Following the documentation, create this
Cartfile
:Running
carthage update
generates mismatched versions inCartfile.resolved
:If we manually change all the versions to
6.29.0
inCartfile.resolved
then runcartfile bootstrap
,Carthage
will throw the following error:However:
6.29.0
(FirebaseAnalytics-1339166ebecfac2a.zip)6.29.0
(FirebaseCrashlytics-d0d6346298c14328.zip)I was able to manually download the zip listed in the
Binary.json
files for6.29.0
and place them, and everything worked fine, so I assume there is a problem with how Carthage resolves those FirebaseBinary.json
files?Based on contributions and activity on other issues, I believe this might be a question for @paulb777?