Why do you need a shared static property on AppModel? This is obviously just a demo project to demonstrate the issue. In my real project, that property has to be accessible from other parts of the app Since Folder conforms to identifiable in SidebarView could you just use ForEach(folders) { folder in? Doesn't make a difference. The crash output looks like this: @ObservationIgnored private let _$observationRegistrar = Observation.ObservationRegistrar() internal nonisolated func access<Member>( keyPath: KeyPath<AppModel , Member> ) { _$observationRegistrar.access(self, keyPath: keyPath) } internal nonisolated func withMutation<Member, MutationResult>( keyPath: KeyPath<AppModel , Member>, _ mutation: () throws -> MutationResult ) rethrows -> MutationResult { try _$observationRegistrar.withMutation(of: self, keyPath: keyPath, mutation) --> Thread 1: Simultaneous accesses to 0x281bcc760, but modification requires exclusive access } @ObservationIgnored private var _selectedFolder: Folder? = nil

Also, this seems to be specific to the list selection in the sidebar in NavigationSplitView as I'm using the same app model elsewhere in my project and everything works fine. I did have the same crash in another part of my project where I use a similar UI, which was also using the app model. In that particular case, I could remove the property from the app model, which solved the issue.

I have the same issue if I run Xcode 15 on Ventura but it's fine on Sonoma. Were you able to fix this issue?

Still an issue with Beta 8. Perhaps beta 9 (if there's an update this week), RC or even 17.1 😬

Was fine on macOS but now borked in the latest RC.

I could use a List but it's not as powerful as a Table. I want to achieve something similar that you can find with Finder. It's most likely on Apple's list (no pun intended) already but had other priorities. Let's hope for iOS 18 and macOS 15!

Exporting and importing worked exactly once for me, then it stopped working for no apparent reason. No changes were made in the project settings. Disabling "Localization Export Supported" doesn't help. It seems Xcode has some issue with a subproject that doesn't even include any localization. I'm going to have to spend a week importing hundreds of strings in 10 different languages manually.

Hi, sorry for the late reply. Notifications were on for that thread but off in my profile for some reason. And for some odd reason, export/import is now working. I have no idea why or how. The only thing I can think of is either the derived data was is an odd state (even if I cleared it several times) or it occurred because some languages were incomplete or perhaps there was an issue in one of the languages? Now that all languages are complete (manually copied strings over), import and export now works. Odd. I'll file a bug report if the issue occurs again.

Please see FB13334609

Seems like this is normal behaviour and that somehow the sub hasn't auto renewed but I would still assume that it should return a unverified result if there are not transactions?

Answering my own question: yes.

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?

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!

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.

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