ZDKObservationToken is implemented in both MessagingAPI and ChatProvidersSDK error | Community
Skip to main content

ZDKObservationToken is implemented in both MessagingAPI and ChatProvidersSDK error

  • March 6, 2022
  • 5 replies
  • 0 views

I'm seeing the following error in the debugger console:

objc[76025]: Class ZDKObservationToken is implemented in both /MyProject/Build/Products/Debug-iphonesimulator/MessagingAPI.framework/MessagingAPI (0x1088bf6c8) and /MyProject/Build/Products/Debug-iphonesimulator/ChatProvidersSDK.framework/ChatProvidersSDK (0x109be0b60). One of the two will be used. Which one is undefined.

These following frameworks are imported for our Zendesk Chat feature. Removing any results in compiler error:

import ChatSDK
import ChatProvidersSDK
import Foundation
import MessagingSDK

Specifiying Zendesk in Package.swift:

// swift-tools-version:5.5
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: “My”Project,
    platforms: [.iOS(.v14)],
    products: [
        .library(
            name: "ZDesk",
            targets: ["ZDesk"]
        )
    ],
    dependencies: [
        .package(
            name: "ZendeskChatSDK",
            url: "https://github.com/zendesk/chat_sdk_ios",
            .upToNextMajor(from: "2.0.0")
        ),
        .package(
            name: "ZendeskSupportSDK",
            url: "https://github.com/zendesk/support_sdk_ios",
            .upToNextMajor(from: "5.0.0")
        )
    ],
    targets: [
        .target(
            name: "ZDesk",
            dependencies: [
                "ZendeskChatSDK",
                "ZendeskSupportSDK"
            ]
        )
    ]

5 replies

Greg29
  • March 9, 2022

Hi Eric! Just so that I know how to prioritize this, is this blocking the app from compiling or are you just ensuring that you're clearing errors? 


Greg29
  • March 9, 2022
Hi Eric

  • Author
  • March 10, 2022

Hi Greg - not blocking compilation, but I would like to know what the issue is and whether there something I should be doing to prevent this. My guess is that it's a linking issue on your side.

Thanks for checking


  • Author
  • March 10, 2022

Greg29
  • March 10, 2022
Hey, thanks for doing my job for me Eric and apologies for missing that myself! Good catch and good to know for now. I do know that some dev teams have a zero warning policy, so hopefully this is something that'll be resolved sooner than later for those people.