Actually, I think I found the issue. After some further investigation, it seems the issue occurs when UIPointerStyle.hidden() is used: func pointerInteraction(_ interaction: UIPointerInteraction, styleFor region: UIPointerRegion) -> UIPointerStyle? { return UIPointerStyle.hidden() } Using UIPointerStyle.system() instead prevents the cursor from jumping. Apple folks: FB13709727

Apple folks: FB13708422 It would really be nice to disable eye tracking for the hover gesture so it can behave like it does on iPadOS.

No, sorry.

Making ControlActiveState available on visionOS would solve this issue. It's only available on macOS at this time. FB13675635

Is this ever going to get fixed? Some users are unable to make any in-app purchases on the Mac App Store! It's not just our app - we asked users running into this issue to try purchasing IAP from other apps and that fails as well. If anyone has a workaround I'd love to know about it!

This has been fixed in the latest iPadOS 17.4 beta, BTW.

Even better workaround: struct DetailsView: View { @Environment(\.dismiss) private var dismiss @Binding var selectedFolder: Folder? var body: some View { VStack { if let folder = selectedFolder { Text(folder.name) } else { Text("No selection") } } .toolbar { ToolbarItem(placement: .cancellationAction) { Button { dismiss() } label: { Text("Cancel") } .id(UUID()) } ToolbarItem(placement: .confirmationAction) { Button { dismiss() } label: { Text("Save") } .id(UUID()) } } } }

Found a workaround: struct DetailsView: View { @Environment(\.dismiss) private var dismiss @Binding var selectedFolder: Folder? @Environment(\.scenePhase) private var scenePhase @State var refreshID = UUID() var body: some View { VStack { if let folder = selectedFolder { Text(folder.name) } else { Text("No selection") } } .onChange(of: scenePhase) { _, newPhase in refreshID = UUID() } .toolbar { ToolbarItem(placement: .cancellationAction) { Button { dismiss() } label: { Text("Cancel") } .id(refreshID) } ToolbarItem(placement: .confirmationAction) { Button { dismiss() } label: { Text("Save") } .id(refreshID) } } } } Forcing an ID refresh seems to work but still, this should be fixed.

Additionally, we have a user reporting a -1008 error (NSURLErrorResourceUnavailable) on macOS. iOS is unaffected. Does Apple even care about the MAS? It's not even able to process offer codes and now this. I understand the App Store on macOS is far from being the goldmine it is for Apple on iOS but come on! It's a bad user experience.

This seems to be an ongoing issue: https://developer.apple.com/forums/thread/724084 https://developer.apple.com/forums/thread/728586 FB13505887

Seems very familiar the issue we've been experiencing: https://developer.apple.com/forums/thread/743789 Have you ever found the cause/solution?

Seems very familiar the issue we've been experiencing: https://developer.apple.com/forums/thread/743789 Have you ever found the cause/solution?

I was able to somewhat reproduce the issue under macOS 14.3 B3 but eventually it worked. Not sure if either of these actions helped: Closed the app and relaunched it Launched another subscription app (ex: Photomator), initiate a purchase, cancel it and then relaunch our app Advice from the StoreKit team would be appreciated.

Here's our use case: instead of a non-consumable IAP (NCIAP), we went with a non-Renewing Subscription (NRS), which doesn't support Family Sharing for some odd reason? Is this by feature, by the way or just an omission? So in order to "fix" this, we created a free NCIAP, available only to users that purchased the NRS so that they can "upgrade" for free and share their purchase with their family. The issue we have is that the purchaser could potentially get a refund for the NRS. In such case, we can detect that refund and invalidate the free NCIAP on the purchaser devices but not for those who share the purchase. As far as I know, there's no way to link the NCIAP with the purchaser in order to validate the transaction ID and invalidate it in case of a refund. Or, is there some other workaround to achieve this? Thanks!

Hi. Has this changed since? Is the transaction order id shared between the purchaser and the family member now or is there a way to link them together?