Do you have an iCloud backup ? If so, do as instructed here: https://support.apple.com/en-gb/HT204184

Maybe there is a network issue that does not show on your side. Could someone in another location try to reproduce the problem on the TestFlight version ?

There are visibly some issues with curl when dismissing. In some cases, animation doesn't work. https://stackoverflow.com/questions/62187639/swift-modal-transition-partial-curl-on-dismiss-got-stuck Could you test with another type of animation: transitionFlipFromLeft

I would not do it this way, but just create a set of perfect square and train the model to recognise perfect square. Then test with "unperfect squares" and you should get the score directly. Otherwise, how would you create your different categories (from nearly perfect to totally not ? And the training will just confuse the classifier. Different categories that could make sense are shapes: Perfect Square, perfect Circle, Perfect Triangle, Perfect Pentagon…

Announced in Xcode 13.2 RC: New Features Xcode 13.2 includes support for app projects you create with Swift Playgrounds 4. (84436977)

When reading doc, it seems you do it in the proper order. But if I may ask: why do you need to add childView instead of subview ? Is the view so complex that it needs its own controller ?

To remove all constraints on a view: func removeAllConstraintsFromView(view: UIView) { for c in view.constraints { view.removeConstraint(c) } }

I tested in Xcode 13.2RC and could create it:

How would you make the difference between user pressing button to change volume (what he/she must always be capable of) and pressing to start a timer without changing the volume ? So I fear there is no way to do this whilst being compliant.

I do not see how you react to startDateLabel tap. Is there a gesture ? Or is it through cell selection ? In this case, reselecting the same cell does not trigger the delegate func for select/deselect. Could you show the delegate func cellForRow at ?

From Swift 5, pods should be compatible with newer versions of API (forward compatibility). API deprecation is another issue, because that's not the API that changes, it's the OS that does not support it anymore. So using old Xcode may not work (and anyway, you will not be able to submit to Appstore). So if pods are yours, you will have to update for those deprecations. Could you show some examples of Swift5 warnings and of deprecation ?

Which version exactly ? In which conditions ? At start, when editing, when compiling… ? Which MacOS version ?

As of the documentation we've found no robust solution so far. That's because there is no robust solution.

Where do you look ? In Xcode > Preferences > Account ? Which version of Xcode ?

Do you really run this in playground ?