Post

Replies

Boosts

Views

Activity

Reply to _dispatch_client_callout crash
Did you figure things out? I am see a very similar stack trace during a TestFlight test - and I am not quite sure how to track it down 0 libsystem_kernel.. _pthread_kill 1 libsystem_pthre…. pthread_kill 2 libsystem_c.dylib abort 3 libc++abi.dylib abort_message 4 libc++abi.dylib demangling_terminate_handler() 5 libobjc.A.dylib _objc_terminate()| 6 libc++abi.dylib std::_ terminate (void (*)()) 7 libc++abi.dylib std::terminate() 8 libdispatch.dylib _dispatch_client_callout <--- 9 libdispatch.dylib _dispatch_root_queue_drain 10 libdispatch.dylib _dispatch_worker_thread2 11 libsystem_pthre. _pthread_wathread 12 libsystem_pthre.. start_wathread
Dec ’23
Reply to macOS TestFlight app using Xcode environment for IAP
I've run into a similar thing. I have local IAP testing setup. And usually it works OK. Then after whatever reason it stops. It seems to expect a local server that acts as a AppStore mock. But that server has crashed. The sad thing - I have to reboot the machine to bring it back up and get it working again. It would be lovely if the Xcode/StoreKit2 team would fix this. I suspect there might be a way to somehow restart the service. But I haven't figured out how. One would have expected restarting Xcode should be all it takes but... that does not seem to be the case. Dear Apple - do better.
Nov ’23
Reply to Mac AppStore Stuck in Review due to Meta Data Policy
Some real users will be even more clueless I agree - to a point. But if a user (or reviewer) does not know that a barcode has to be seen by the camera in full - there isn't really much to help or do. 🤷‍♂️ At least the reviewer realized that this was a bogus problem. if they don't like a new feature, just remove it from the app. It's pointless trying to interact with them in any way. I am supporting an API that was added in macOS 12. Removing it just because a reviewer claims it's "pre-release" (while the Apple website states it is not) feels like the wrong move. Then I would rather try another submission and hope for a different reviewer. After only a week, I'd say "be patient, just wait". Thanks for that feedback!
Jul ’22
Reply to Shortcut is failing to run via Scripting Bridge
@jbenavidesv good findings - but for me it still hasn't changed things. Are you sure there isn't something more you did? Let me run quickly though my current setup: Info.plist: Entitlements: And runtime:      guard       let app: ShortcutsEvents = SBApplication(bundleIdentifier: "com.apple.shortcuts"),       let shortcuts = app.shortcuts else { throw "error" }     print("getting short")     guard let shortcut = shortcuts.object(withName: name) as? Shortcut else { throw "error" }     print("running short", shortcut)     let res = shortcut.run?(withInput: input)     print("shotcut result", res ?? "nil")
Feb ’22