mixpanel/mixpanel-iphone

Cocoapods: duplicated headers

alistra opened this issue · 4 comments

Integration Method: CocoaPods
Xcode Version: 13.2.1
Library Version: 4.1.0
Platform: iOS
Language: Swift
Description:

When integrating with Cocoapods, there are warnings related to duplicate headers in build phase and in fact the headers are duplicated there.

Screenshot 2022-01-19 at 13 34 35

Screenshot 2022-01-18 at 16 02 01

Expected Behavior:

There should be no warnings.

Yeah, I'm also getting [!] [Xcodeproj] Generated duplicate UUIDs: after pod install, with the following duplicates:

AutomaticEvents.h
AutomaticEvents.m
MPDB.h
MPDB.m
MPFoundation.h
MPJSONHander.h
MPJSONHandler.m
MPLogger.h
MPLogger.m
MPNetwork.h
MPNetwork.m
MPNetworkPrivate.h
Mixpanel.h
Mixpanel.m
MixpanelExceptionHandler.h
MixpanelExceptionHandler.m
MixpanelGroup.h
MixpanelGroup.m
MixpanelGroupPrivate.h
MixpanelIdentity.h
MixpanelIdentity.m
MixpanelPeople.h
MixpanelPeople.m
MixpanelPeoplePrivate.h
MixpanelPersistence.h
MixpanelPersistence.m
MixpanelPrivate.h
MixpanelType.h
MixpanelType.m
SessionMetadata.h
SessionMetadata.m
c.h
umbrella.h

Version: 4.1.0

Integration Method: CocoaPods 1.11.2
Xcode Version: 13.2.1
Library Version: 4.1.0
Platform: iOS
Language: Objective-C

I get the following warnings when building our app:
Skipping duplicate build file in Copy Headers build phase: /Users/lee/Desktop/app directory name redacted/Pods/Mixpanel/Sources/Mixpanel.h
Skipping duplicate build file in Copy Headers build phase: /Users/lee/Desktop/app directory name redacted/Pods/Mixpanel/Sources/MixpanelGroup.h
Skipping duplicate build file in Copy Headers build phase: /Users/lee/Desktop/app directory name redacted/Pods/Mixpanel/Sources/MixpanelPeople.h
Skipping duplicate build file in Copy Headers build phase: /Users/lee/Desktop/app directory name redacted/Pods/Mixpanel/Sources/MixpanelType.h

The Xcode recommended changes contain a section to correct this (as shown on the screen capture, below). That works until the next "pod install" is run, then the errors come back.

Screen Shot 2022-01-20 at 7 24 38 PM

@alistra @oronbz @lhasiuk thanks, we will look into this and get it fixed

hi @alistra, this has been fixed in v4.1.2. Thanks for bringing it up. I'm closing it now, please feel free to reopen if the problem still exists.