New issue
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
GoogleUtilities installed twice, impossible to archive app on Xcode 11.x #4087
Comments
This comment has been minimized.
This comment has been minimized.
Looks like a duplicate of #2166. See that issue and CocoaPods/CocoaPods#8206 for workarounds. |
As a workaround, I put the GoogleUtilities dependencies as separate pods in my Podfile, before the Firebase pods are resolved and it fixed the issue. These were based off my current Podfile.lock: pod 'GoogleUtilities/AppDelegateSwizzler' |
I'm having the same issue. platform :ios, '13' target 'SarahClass' do target 'SarahClassMac' do Note I dont have FirebasePerformance. I noticed that the Podfile.lock has entries like:
|
@workingDog Does @ibuprofane's workaround work for you? |
no it doesn't. I've tried putting the GoogleUtilities dependencies in my SarahClass target, then in the SarahClassMac target, without success. I get the same warning message. Each time I did a DerivedData purge and recompile. I also tried the pod script solution proposed in https://medium.com/@GalvinLi/tinysolution-fix-cocoapods-duplicate-implement-warning-5a2e1a505ea8 That did not work either. |
Just to be certain, did you put the dependency pods BEFORE the Firebase pods? Mine looks like: pod 'GoogleUtilities/AppDelegateSwizzler' |
yes |
@workingDog That medium post is about a different issue than the archive problem with GoogleUtility subspec combinations discussed here. |
Update on my experiments on making GoogleUtilities archive with my 2 targets. I have put the GoogleUtilities dependencies in my second target "SarahClassMac". But when I try to archive I now get this error: .../sarahclass/Pods/gRPC-Core/src/core/tsi/ssl_transport_security.cc:45:10: |
Did a clean DerivedData, clean build ... and now archive is working. |
This one solved my issue, thank you @paulb777 |
It looks like the issue here is resolved, so I'll be closing it now. Otherwise, if you're still experiencing this problem and want to continue the discussion, just leave a comment here and we're happy to re-open this. |
I have the same problem and can't find any solution or workaround. I've been modularizing my app and faced with this problem after I've moved some code in separate module inside separate project in common workspace:
Analytics framework connected with the app as regular framework (not through Cocoapods) I had en warning and can't archive the project.
My Podfile:
Xcode 11.1 / Cocoapods 1.8.4 Have anybody thoughts how solve it? |
I suggest investigating and resolving the difference between GoogleUtilities-ac14cd06 and GoogleUtilities-00567490 |
I've solved the issue. It was a lot of fun! First, I've compared main app target (MyApp) and module target's build settings to be sure that two targets are using the same swift version / c/c++ compiler and its options thanks to @paulb777. Some was different, but setting up the same value in both targets didn't help. Then I've continued searching the difference and have dove into CocoaPods sources. I've figured out that CP uses deduplication mechanism while it generating targets for Pod project. CP calculates hash using specs, platform and build type for each target. I've added additional logging to PodVariant constructor:
and figured out that platform and build type was the same, but specs included different set of pieces of GoogleUtilites. That was a point! Main target was depend additionally on GoogleUtilites/UserDefaults because of dependency on other Firebase parts. So, solution was to create full single set of GoogleUtilities parts:
and use it definition in both targets in Podfile. Now I have only one GoogleUtilities target in Pod project and all warnings gone. If you faced with similar problem:
Hope it help to somebody. |
[READ] Step 1: Are you in the right place?
file a Github issue.
with the firebase tag.
google group.
of the above categories, reach out to the personalized
Firebase support channel.
[REQUIRED] Step 2: Describe your environment
Using Auth0 (1.19.0)
Using Crashlytics (3.14.0)
Using Fabric (1.10.2)
Using Firebase 6.10.0
Using FirebaseABTesting (3.1.2)
Using FirebaseAnalytics (6.1.3)
Using FirebaseAnalyticsInterop (1.4.0)
Using FirebaseCore (6.3.1)
Using FirebaseCoreDiagnostics (1.1.1)
Using FirebaseCoreDiagnosticsInterop (1.0.0)
Using FirebaseDynamicLinks (4.0.5)
Using FirebaseInAppMessaging (0.15.5)
Using FirebaseInstanceID (4.2.5)
Using FirebaseMessaging (4.1.6)
Using FirebasePerformance (3.1.5)
Using FirebaseRemoteConfig (4.4.2)
Using GTMSessionFetcher (1.2.2)
Using GoogleAppMeasurement (6.1.3)
Using GoogleDataTransport (3.0.1)
Using GoogleDataTransportCCTSupport (1.2.1)
Using GoogleToolboxForMac (2.2.1)
Using GoogleUtilities 6.3.1
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Using Xcode 11.x the app compile with this warning on my target:
But is impossible to archive it because of this error:
During archiving the following warnings show up on GoogleUtilities:
Warning Group GoogleUtilities-00567490 Group:
Warning Group GoogleUtilities-ac14cd06 Group:
Important:
By removing FirebasePerformance (that remove also GTMSessionFetcher and GoogleToolboxForMac) the error is gone and everything works perfectly.
Thank you for your help!
The text was updated successfully, but these errors were encountered: