Compile error when updating to Segment 4.1.1, 'Analytics' framework was renamed to 'Segment' in Segment 4.1.1

[leandromperez]

After a pod update:

• Installing Analytics 4.1.1 (was 4.0.5)
• Installing Segment-CleverTap 1.1.7
  

Changing 'Analytics' to 'Segment' where it corresponds, seems to fix the issue:
E.g. #import <Segment/SEGAnalyticsUtils.h> instead of #import <Analytics/SEGAnalyticsUtils.h>

[Aditi3]

Hi @leandromperez

I quickly checked the release notes of Segment Analytics. Looks like in their version 4.1.0 they have renamed module from Analytics to Segment.

Thanks so much for the heads up! We'll add a fix for it in our next release.

[Aditi3]

We've shipped the release with the required changes.
Here is the link to the latest release that comes with the fix: https://github.com/CleverTap/clevertap-segment-ios/releases/tag/1.1.8

Thanks again @leandromperez for reporting.

[leandromperez]

@Aditi3 Thanks for that.
Running pod deintegrate + pod update is installing the latest version of Segment (4.1.1) and Segment-Clevertap (1.1.8).
But the build is failing because the Analytics.framework is not present in the link phase. It should be trying to link Segment.framework instead right?

ld: framework not found Analytics
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Any ideas?

[Aditi3]

In my Example Project, Segment.framework is getting linked.

Link to Starter Application: https://github.com/CleverTap/clevertap-segment-ios/tree/master/ExampleSwift

Try clearing the Xcode and Pod cache?

[leandromperez]

Aditi, Thank you for the response. The problem was an old flag left in Other Linker Flags. It seems that the old Analytics flag wasn't removed. Everything is working now. Best, Leandro

…

On Wed, Nov 11, 2020 at 12:47 AM Aditi Agrawal ***@***.***> wrote: In my Example Project, Segment.framework is getting linked. Link to Starter Application: https://github.com/CleverTap/clevertap-segment-ios/tree/master/ExampleSwift Try clearing the Xcode and Pod cache? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAZTBECRLGL2X5D5UEAQJLSPICOZANCNFSM4TPLU2YA> .