Were you able to find an answer?

Still seeing this problem where majority of responses not delivered to the completion handler on iOS 14.0.1. Is this known issue?

Thanks. Maybe documentation should say something about it - spent 5 hours trying to figure out what I was doing wrong, before posting here and on stack overflow.

Using AppKit windowShouldClose works when debugging in Xcode, but not when running in release mode on Big sure. Does anyone know what's going on here?

Glad to know its not just me :)

Hi I know its an old thread, but I'm trying to find an answer and this seems like a good place. There is an app on Mac App Store, a new app, that simulates user input, and it seems it's doing it while being sandboxed. Is there some new APIs that were introduced, or something changers re sandboxing rules that's it allowed now? https://apps.apple.com/us/app/remmo-remote-mouse-keyboard/id1598906173 I'm have a similar app and I have to distribute it like Matt outside of the store, and I wonder if there was a change that can allow me in. Best regards

Hi. Have you figured this ../YES thing out?

Haha... asked and then remembered --- need to set GENERATE_INFOPLIST_FILE to NO in order for this to work.

#0 0x00000001e14dc0a0 in kevent_id () #1 0x0000000104b52ebc in _dispatch_kq_poll () #2 0x0000000104b538e0 in _dispatch_event_loop_wait_for_ownership () #3 0x0000000104b3fc3c in __DISPATCH_WAIT_FOR_QUEUE__ () #4 0x0000000104b3f598 in _dispatch_sync_f_slow () #5 0x00000001a280d018 in -[NSUbiquitousKeyValueStore _synchronizeForced:notificationQueue:] ()

I'm now seeing this happening in tvOS 15.6 :(

I'm calling NSUbiquitousKeyValueStore.default.synchronize on app entering foreground like its suggested in https://developer.apple.com/documentation/foundation/nsubiquitouskeyvaluestore/1415989-synchronize, and its doing it async on another thread, then I'm trying to access an object via NSUbiquitousKeyValueStore.default.object:forKey: and the app gets stuck cause I'm doing it on main thread. @eskimo FB11037643

Stack trace

My solution is to get the bounds of the the self.superview.superview -> _UINavigationBarTitleControl, instead of relying on the bounds of the self.superview -> _UITAMICAdaptorView.

Same here... app id 629019487, iOS app have been stuck "In Review" for days. When I contacted @AppReview - got a response "I can confirm that your app is in the "Ready for Sale" status on the App Store as of Sep 8, 2022.", but that's macOS app, and not iOS app that was approved on Sep 8, 2022. Any help would be appreciated @Andreas, as this update fixes a crash that really bugs my users.

In my experience, in order to change Mac Catalyst executable name (Name.app), I had to change PRODUCT_NAME in the Xcode project.