[quote='815147022, DTS Engineer, /thread/766035?answerId=815147022#815147022'] SO, making sure this is clear, the performance "trick" here is to use your final scan storage format as your "intermediate" format instead of doing the entire scan in memory. If done properly, this means: [/quote] I'm not sure I understand. Do you mean that you would write the scan results to disk while the scan is in progress? Otherwise I don't get the "entire scan in memory" part. You're probably right that resuming a scan is easier in the iterative case. I'm not supporting that case (yet), so for now I'll stick to recursion.

After replacing the .heic images with .png ones, it finally worked.

[quote='815279022, DTS Engineer, /thread/769257?answerId=815279022#815279022'] I don't know where the VFS driver got that st_size from, but returning a size >~18 Exabytes seems like an unusual choice. [/quote] Thanks for pointing out the size issue. Today Paragon got back to me and confirmed that the developers will fix the wrong size returned for symbolic links.

In the meantime I already filed FB15737374 and opened Case-ID 10297510 to discuss a different issue I'm having, and the TSI engineer suggested as a workaround to update the SpriteKit scene in its SKScene.update(_:) method (although the delegate methods seem to work as well), which poses the question of how to avoid race conditions when accessing my custom data needed both in SceneKit and in SpriteKit (since the first uses its own thread, and the latter is annotated @MainActor). For now, it is proving to be a difficult conversation.

[quote='817975022, DTS Engineer, /thread/767019?answerId=817975022#817975022'] Dispatching to the main thread (with a Swift Task) is an anti-pattern in this case [/quote] Correct, and as I mentioned, this poses the question of how to avoid race conditions when accessing my custom data needed both in SceneKit and in SpriteKit (since the first uses its own thread, and the latter is annotated @MainActor).

Here's a link to a sample project: https://www.swisstransfer.com/d/e8ad8888-ae2e-4371-8e82-0d5915c967c7 I really just created an empty macOS App project, added a target App Intents Extension named CompareIntent, and pasted the code I provided above in the CompareIntent.swift file. Then I build the project and copied the app into my Applications folder, and I can still reproduce the issue when running the app intent in Shortcuts.

Do you mean to the main target or the app extension? And should I keep the existing Localizable.xcstrings or delete it?

I just had this issue again on my own Mac with macOS 15.2. My app had been active for a while and had been able to resolve bookmarks. Then suddenly when trying to create new bookmarks I got the usual error. Restarting the app solved the issue.

[quote='818239022, DTS Engineer, /thread/764435?answerId=818239022#818239022'] The app is running for a significant period of time. [/quote] I had launched the app at most a couple hours earlier. I had the app running for weeks before and never had this issue.

[quote='818356022, DTS Engineer, /thread/770279?answerId=818356022#818356022'] App Shortcuts need to be in your main app target [/quote] I have a non-SwiftUI app, so I guess this doesn't apply? I don't see how I could have App Shortcuts without a separate App Intents Extension. Is this AppShortcuts.xcstrings officially documented? I couldn't find it anywhere.

I'm having the same issue. I tried increasing the build number and still the build appears shortly on the website in the "Processing" state, and then disappears. After the first upload I got an email with an error message, which I resolved and haven't got any email since, but still any uploaded build is not listed on the website. Then I tried increasing the version string from 1.0 to 1.0.1 and the build number as well, and after reloading the website it showed a disclosure indicator with the label 1.0.1, but completely empty. After reloading the website one more time, even this indicator was gone again, and the website is completely empty like at the start of this whole experiment.

Until now it seemed that the customer‘s very old hardware was the cause of this odd behaviour, but they just contacted me again telling me that they upgraded the hardware and the looping still happens. Latest Gigabyte motherboard and Intel i5-14400. All new hard drives – everything new. Latest Windows 11 Pro OS (formerly using Windows 10 Pro – 2 years ago latest update). Do you think it’s still the hardware, or macOS, or Windows?

[quote='818356022, DTS Engineer, /thread/770279?answerId=818356022#818356022'] App Shortcuts need to be in your main app target [/quote] I don't follow. Currently I have an App Intents extension as a separate target and the Shortcuts app lists the intents defined there, even without me defining anything in the main target. That's why I assumed you were talking about SwiftUI. If that's not the case, I don't understand what AppShortcutsProvider is meant for. What confuses me even more is that I have a different Xcode project with an App Intents extension that contains a Localizable.xcstrings file, and Shortcuts displays those string just fine.

I'm glad to see how developer support changed in the last years, and now in particular. I think offering support on the forums that everyone can see and then allowing to request free support via TSI when the forum doesn't help is going to resolve a lot of the problems that I personally had with TSI.

I've now removed the App Intents Extension and moved the code to the main target. @available(macOS 13.0, *) struct MyShortcuts: AppShortcutsProvider { static var appShortcuts: [AppShortcut] { AppShortcut(intent: MyIntent(), phrases: ["Do something in \(.applicationName)"]) } } @available(macOS 13, *) struct MyIntent: AppIntent { static let title = LocalizedStringResource("intent.title") static let description = IntentDescription("intent.description") static let openAppWhenRun = true @Parameter(title: "intent.parameter.first") var first: String @Parameter(title: "intent.parameter.second") var second: String func perform() async throws -> some IntentResult { return .result() } } I've also created AppShortcuts.xcstrings in the main target. When I build the project, AppShortcuts.xcstrings only contains the string Do something in \(.applicationName), while all other strings (intent.title etc.) appear in Localizable.xcstrings. Is this expected? Previously, when I still had the separate App Intents Extension, I had all those strings in the same file, but when I renamed it to AppShortcuts.xcstrings and moved it to the main target I got several errors Invalid Utterance. Every App Shortcut utterance should have one '${applicationName}' in it. The errors went away when I only kept the string Do something in \(.applicationName), although I had to remove the others manually from the source code editor, since the string catalog editor always disables the buttons to add and remove strings in AppShortcuts.xcstrings.