Same

I have the same question.

I had created my own edit menu after apple disabled the default pencil kit one originally mentioned in this post. I just realized that them re-enabling it in iOS17 is collliding with the custom one I had created and I am seeing no way of making them play well together. In the off chance that you're going through the same thing @Alan_Z , would you happen to know how to add some items to pkcanvasview's edit menu?

Heads up @Alan_Z , we're now at iOS17 and Apple has reintroduced the default tap on canvas to open the default edit menu behaviour mentioned in this post. Of course this has broken my app again 😂. Thanks Apple I guess.

Would love to have a way of getting the strokes selected by PKLassoTool too, its kind of a core feature imo.

Same issue here, did you ever resolve it?

Hi @App Store Commerce Engineer, is there a way to programmatically know if the user cant access their currentEntitlements due to an internet or other error? If a user has no internet when they first open an app in wihch have previously purchased some items on another device, they will not get access to these items on the device with no internet. This makes perfect sense, but we should have a way to inform the user of this. When this happens I get the following error in Xcode: Error enumerating all current transactions: Error Domain=NSURLErrorDomain Code=-1009 "The Internet connection appears to be offline." UserInfo={AMSStatusCode=0, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <33FA368E-0213-4D4D-AF53-C93CE9E32018>.<1>, NSErrorFailingURLKey=https://mzstorekit-sb.itunes.apple.com/inApps/v1/history?guid=00008027-001970E00185002E&reason=initial, _kCFStreamErrorDomainKey=1, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask <33FA368E-0213-4D4D-AF53-C93CE9E32018>.<1>" ), NSLocalizedDescription=The Internet connection appears to be offline., NSErrorFailingURLStringKey=https://mzstorekit-sb.itunes.apple.com/inApps/v1/history?guid=00008027-001970E00185002E&reason=initial, NSUnderlyingError=0x281c314d0 {Error Domain=kCFErrorDomainCFNetwork Code=-1009 "(null)" UserInfo={_NSURLErrorNWPathKey_desc=unsatisfied (No network route), _kCFStreamErrorCodeKey=50, _kCFStreamErrorDomainKey=1}}, _kCFStreamErrorCodeKey=50} Which is great, but I can't catch it anywere in my code to trigger UI changes. Do you know how could I catch this error? Best, Joaquín.

Hey, where you able to resolve this?

Same issue here

It seems you're not the only one having performance issues with swift charts: https://developer.apple.com/forums/thread/710597?login=true&page=1#751479022

Same issue, distilled it down to a very simple example with around 100 hardcoded datapoints, and transitions in and out of the view containing the chart in a navigation stack has noticeable lag. Its a really simple chart, it shouldn't have any lag at all.

The issue is still present when using toolbar instead of navigationBar.

@Alan_Z thank you for posting this solution! I've been trying to figure out what happened with PKCanvasView's edit menu and your answer is the only mention of what happened I've seen on the internet! Sometimes it is truly hard to understand how Apple can make such a drastic change to one of their libraries and make no mention of it at all. I've managed to get your solution running, and now I am facing the same issue you've mentioned, namely having to modify the paste method, for among other things, setting in which location of the canvas to paste. I was wondering if you've managed to find an elegant solution to this that correctly updates the undo manager, and if so if it would be possible for you to share it. Again, thank you. You've already been exceedingly helpful by virtue of your above answer alone.

Did you find a solution for this? It makes no sense that we can't chose the failure threshold ourselves!

Hi, I had this exact crash reported by several users, its very very sporadic but it does happen. I think it's due to me using a queue like this one to render PKDrawings on a lazy grid view: DispatchQueue(label: "thumbnailRenderingQueue", qos: .userInteractive, attributes: .concurrent). Here are the logs just in case you can take a look at them. crash.txt Thank you!