'shared' is unavailable: not available on iOS (App Extension) on Xcode 13 beta 3

[iterable]

'shared' is unavailable: not available on iOS (App Extension) on Xcode 13 beta 3

[tapashmajumder]

Hi @paulmesa-paypal we officially do not support beta version of Xcode. We only support the latest released version of Xcode.

We will try to take a look at this if this is an easy fix.

[kylebrowning]

The Athletic. I'll raise a new support ticket, thanks.

[paulmesa-paypal]

Here is an example fix in the braintree iOS sdk braintree/braintree_ios@89912f4

[tapashmajumder]

Thank you for all the links provided.

[kylebrowning]

Here's the fix:

https://twitter.com/twannl/status/1415643866414338054

[paulmesa-paypal]

Understandable! @tapashmajumder I do have a fix up on a fork that we've been using for development here master...paulmesa-paypal:pm/july/SteelThread but I havent verified any behavior outside of the small subset that we use. This also marks entire classes as unavailable whereas the final solution might involve making only certain functions unavailable

[kylebrowning]

Just want to reiterate, this makes Xcode beta's impossible to use without removing Iterable entirely.

I know that you dont support betas, but I just want to highlight that this means we can't work on features in coordination with Apple to launch along side the release of iOS 15.

It is extremely debilitating to have to remove Iterable each time we need to work on an iOS 15 feature in anticipation of the launch.

[tapashmajumder]

@kylebrowning Can you please escalate this issue using your CSM for Iterable? Which company do you work for?
This way we can prioritize this issue with urgency if needed.

[kylebrowning]

I opened a ticket, got a response a day or so later, but I havn't heard back since. At any rate, it looks like Apple has reverted this change in Xcode Beta 5 and Iterable works again!

[tapashmajumder]

Good to hear this @kylebrowning . In the future if you open a ticket and get no response kindly have the item escalated via your CSM. This ticket did not get escalated to engineering.

I will go ahead and close this issue.

[kylebrowning]

Well I wouldn't say this should be closed, Theres a very real chance you'll have to do this in the future.

[tapashmajumder]

OK. Keeping this open.

[tapashmajumder]

This issue should be resolved with SDK version 6.3.4