Xcode 13.3 Beta 3 - artifact not found for target

Hi Patrick,

Thanks for reaching out. We had an issue with the public artifacts for version 5.4.0 of the Support SDK not being published. This has since been corrected and the artifacts are now available. Do you mind retesting with Xcode 13.3 Beta 3 now please? You should no longer experience the issue. 

This is with v5.4.0 and tried again today with no difference than yesterday, as 5.4.0 is still the newest version.

Attached is all the effected submodules and their versions. The error is the same for all of them.

The problem is that the artifact name needs to match the target name. I solved/worked around this in e.g.

https://github.com/stevenkramer/support_sdk_ios/commit/b0baee520c844d472ade93c4a5fcfd475236b529 

This has to be applied to all binary frameworks though.

The same issue in public Xcode 13.3. How to solve this issue?

We have the same issue with Xcode 13.3 Appstore version.

Depending on your level of desperation, you could fork the package you need and apply the following changes to it and recursively for all its dependencies. In short, the binaryTarget's name and path need to be spelt the same. I created a symlink for the path, instead of renaming the framework.

E.g, this change.

(fixed the link, links are mangled when pasting)

We are facing the following issue:

`artifact not found for target 'ZendeskSupportProvidersSDK'`

Any plans to update https://github.com/zendesk/support_providers_sdk_ios soon?

We are having the same issue as well with xCode 13.3

We are on the public version of Xcode 13.3 and experiencing the same problem. We are pulling the dependencies in using a Package.swift file and not the "Package Dependencies" tab. This was working fine until Xcode 13.3.

artifact not found for target 'ZendeskSupportSDK'

artifact not found for target 'ZendeskMessagingSDK'

artifact not found for target 'ZendeskSDKConfigurationsSDK'

artifact not found for target 'ZendeskSupportProvidersSDK'

artifact not found for target 'ZendeskMessagingAPISDK'

artifact not found for target 'ZendeskCommonUISDK'

We are having the same issue on the App Store version of Xcode 13.3

Same issue here.

The problem is that the artifact name needs to match the target name. I'm not sure, but I having the same issue on the App Store version of Xcode 13.3. Any clue?

I having the same issue on the App Store version of Xcode 13.3. Any clue?

Yes unfortunately this is also present in the final Xcode 13.3 not just the betas, we need Zendesk to resolve this via a Framework update before we can use the Framework with Xcode 13.3.

If you must use Xcode 13.3 there is a workaround posted above by Steven Kramer if you are comfortable forking the framework. 

I was hoping by reporting this issue during the betas they would fix the issue before Xcode 13.3 was finalized, but alas that didn't happen.

Bump, having same issue, had to manually download 13.2.1 to be able to start developing again.

Another bump. This is a simple fix that Steven Kammer has already done. Pointing to Steven Kammer's fork has resolved it temporarily.

Good to know I'm not alone! Just a heads up that this is happening to me with the Chat SDK, as well.

I wish I would have seen this yesterday before I spent the whole afternoon purging and reinstalling Xcode thinking that it was an Apple issue!

Hello,

any news on this? We can not use the latest version of Xcode due this error.

We need a fix asap.

Hey Folks,

Thanks for everyone's patience on this. We are actively working on a fix for this. As soon as I have more info, I'll be posing in this thread.

Hello,

   Any updates on this?

Hey, could you please provide any timeline on this?

This a quick fix for Zendesk Dependencies, working on Xcode 13.3.

Instead of forking, I've created a SPM Package with references to original libs

https://github.com/Dimentar/Zendesk-SP-iOS

Targeting `ChatSDK` + it Dependencies, if you need more, ask, or create PR

No release in sight and it's becoming a big problem!

Please propose a solution quickly

@robert98, for now just downgrade to Xcode 13.2.1. It's the easiest fix until Zendesk can ⌘+F the bad code :-)