This new API is currently only available from macOS Ventura onwards. Previous versions will have to do without.

That is all the code you need. UIApplication.openSettingsURLString is a predefined string essentially provided to you by your app – you don't need to type it out yourself.

Which answer are you referring to?

The whole symbol image frame's centre isn't the same as the centre of the arrow (where you ideally want it to rotate around), if that makes sense. You can add .offset(y: -2) directly to the Image (before the other modifiers), and see if that works. Play around with the offset to get your desired value.

It's because "arrow.clockwise" hasn't got a square frame but "pencil" must have.

The problem is that because you can't modify the contents of the class, you can't tell it to send change notifications which is what SwiftUI needs. I currently trying a way round this, possibly using Combine, but it's difficult without access to the original class (an extension can't do much). I'll update when I get somewhere but it'll either be ugly or not possible.

It worked for me, but I agree – there needs to be a picker to choose which iOS version to target.

If you mean comma, then no it doesn't. The commented part should be a boolean value of whether the URL should be opened in Safari. It's probably not clear enough in the sample code.

This has always been the case since iOS 13.

If that solved your problem, can you please mark that post as being correct, therefore closing this thread and letting everyone else know the issue has been resolved.

Not that I know of. I’m assuming you tried the iOS 15 solution on iOS 16?

I think that’s only for Apple to see, so they can note or forward it on, as I can’t see others’ either.

Can you please close this thread by marking an answer as correct so that others know your issue has been solved.

Make sure your SWDItem and SWDPackage classes are both marked with the @Model macro. Also, you are force unwrapping item.package and maybe that is causing something, I'm not too sure. You might have to show some more code here because there isn't enough to debug the situation.

Using @Bindable could be better as you would have to create this new Binding for every property you need to access. We are still in beta you must remember: things could change.