Xcode 13.3 Beta 3 - artifact not found for target

Unless, hypothetically, you updated your personal phone to 15.4 and don't have any QA devices because you're working from home and need to do stuff that can't be done on the simulator. Hypothetically.

@joe65 you should be able to back-port device support for 15.4 to older Xcode versions. Hypothetically :) 

Hi all,

Thank you for your posts on this issue. We are currently preparing a release of the iOS SDK with a definitive fix for this issue. This will not take long to prepare, I'll update this post in the next day or two once the release is out. Thank you for your patience on this one.

Hi all,

I'm still facing this issue for the last few days. please can someone help

Mick, any updates?

Hello Mick and team, 
please try to give some updates, we are missing out on productive hours. thanks!

Hello,

We're actively working on a release for this issue as a top priority. Apologies for the impact that it is causing. As soon as the release is available, I'll post a link to the release notes here. This should only be a matter of days.

Hi Mick 
Please try to make this a high priority it's already been more than a week. 

Thanks

@mick11

Any updates on this?

@mick11 Is there anyway to escalate/expedite this release going out? A fix has already been identified by other developers and its pretty disappointing that a relatively minor issue with a huge impact hasn't been resolved in a reasonable amount of time.

There are couple of workaround for this:

1. Use Cocoapods (if you are already using SPM and Cocoapods, then this one is easy) to add the package
2. Use the SPM package that @alex137 has created: https://github.com/Dimentar/Zendesk-SP-iOS
3. Try with the official bugfix branch for SPM https://github.com/zendesk/support_sdk_ios/tree/bugfix/Xcode13.3-SPM-integration (note that I have not tried this one)

Mick, time is money :) Any updates?

@dimitar14 Pointing Xcode 13.3's SPM at 'bugfix/Xcode13.3-SPM-integration' works for me btw. (ZendeskSupportSDK, and ZendeskChatSDK)

Honestly, this is a little embarrassing. Please update this. Yes, we are using the workarounds for now but it's been reported on February 25, a fix was given two weeks ago and you have a branch that has the committed changes that was put in almost a week ago. 

All this requires is a tag to the committed branch. 

Hate to pile on but Kevin C hit it on the head. It is great that we have a workaround available (thanks again to those that helped quickly identify the issue and provided solutions) but its unacceptable to expect developers using the Zendesk SDKs to use a bug fix branch when creating a new release/tag off that commit is a trivial operation. Please do what is necessary to escalate this and provide a new release/tag with the appropriate fix ASAP.

@mick11, this doesn't exactly instill trust in the Zendesk brand.

Looks like our long national nightmare is over, an update got pushed earlier today.

Thanks for your patience. We've released a new version of the Classic SDKs which will resolve this issue. Please refer to the release notes below, and thank you again for raising this issue in Zendesk Community!

Release notes:

1. Unified SDK
2. Chat SDK 
3. Support SDK

@mick11 Thanks for the update and informing us of the fixed release's availability on this thread.

I hope your team does a retrospective on this as it should be clear that this was poorly handled from an external perspective and led to a serious loss of confidence in this product by myself and everyone else affected. With the intent of being helpful I'd like to briefly highlight what I view as the two major issues that were at play here:

1. Communication from Zendesk was infrequent at best and when a timeline for the fix was eventually communicated it was pushed multiple times without clear reasoning/explanation as to why. This was particularly confusing given a fix had already been identified and provided weeks prior to this release becoming available.

2. There are too many (paying) developers/apps dependent on this SDK to not be ahead of the curve on issues like this, especially for a company of Zendesk's size and stature. If they are not already, I hope that the team will consider putting resources to work testing the SDK against new XCode beta versions going forward so issues like this can be proactively addressed before they become a problem like this was. And if they were testing against the beta, identifying why this was wasn't proactively addressed prior to the public release or even shortly after should be a focus of the retro. 

If possible it would be great to hear back from you on how the team will prevent issues like this from dragging on in the future. Genuinely appreciate the hard work y'all are doing and thanks again for resolving this issue.

I'm leaving another message just to emphasise that I totally agree and second what was said by @phil49. Couldn't have said it any better. Thank you.

Hi Phil & Mathäus,

We appreciate the feedback. It’s genuinely valued. Yes, we’ll absolutely conduct a formal internal review to fully understand what caused the delay. We do proactively test new versions of Xcode, but there appears to be a sequence of problems that caused this unfortunate situation. We’re sorry for any inconvenience that this caused our customers.

@mick11

Thanks for the updates. Whilst the above releases seem to have fixed the build issue, I think some recent (or this) release has introduced a UI bug which will still prevent us from updating Zendesk/Xcode and I have detailed it here: iOS SDK Live Chat Navigation bar tint color bug

EDIT: Sorry I tagged the wrong person

Thanks Ben,

I'll reply on the post that you've linked to, as this is a different subject.