Posts

Post not yet marked as solved
2 Replies
837 Views
When performing StoreKit 2 operations in my Mac app, even very simple ones like AppStore.sync() a small but steady percentage of users experiences the following error: systemError(Error Domain=NSCocoaErrorDomain Code=4097 \"connection to service named com.apple.storekitagent\" UserInfo={NSDebugDescription=connection to service named com.apple.storekitagent}) Rebooting or re-downloading the App from the Mac App Store, as well as signing out and in again on the Mac App Store does not solve the issue. Strangely enough all of the affected users I'm aware of were initially able to perform In-App purchases via the said app. Without any updates or anything else however suddenly after a restart of the app the above error gets thrown by the system. As I have not found any way to solve this issue yet and the said customers are consequently left without service even though they are paying customers, I am desperate to find help with this issue. Given the simplicity of the AppStore.sync() method for example I can't imagine the solution to lie in code, but I might of course be wrong. Thank you, Bastian
Posted
by betaphi.
Last updated
.
Post not yet marked as solved
1 Replies
537 Views
Hello everybody, I'm working on an app that implements a communication protocol on top of WebSocket using the Network Framework via NWProtocolWebSocket/NWConnection. The issue I'm seeing is that on macOS (at least under macOS 13.0 Ventura) when calling .cancel() on the NWConnection on say the server side, the client does not disconnect gracefully. Instead the client receives a POSIXErrorCode(rawValue: 96): No message available on STREAM on the NWConnection.receiveMessage block. You can verify this behaviour in the testDisconnect() test case in https://github.com/pusher/NWWebSocket (Disclaimer: I'm not the author of NWWebSocket but it shows the same issues that I'm experiencing in my code). The same issue didn't show up in the iOS Simulator, where the connection closed correctly. Now I'm wondering if this is a bug in macOS 13 Ventura or if we can do something about it by changing the disconnect code. Any help is greatly appreciated... Thank you, Bastian Roessler
Posted
by betaphi.
Last updated
.