Did anybody here manage to resolve this? I've run into the same thing and it's still happening all the way up to beta 6.

I am having the same problem with all of the same versions - iOS 15, Xcode 13 and watchOS 8.

+1 from me too, have configured everything as described and receiving the 401. Given that this feature has to be tied to your developer account in some way to count the number of requests you make, and given a 401 error, I would guess that something hasn't been wired up yet to send the right credentials to the API for developer accounts.

+1 from me too, I have also not worked out how to achieve this - I'm guessing that there is a bug or a missing modifier here to allow text to be angled.

Exactly the same problem for me too - I started from an existing widget project and cloned if for a watch widget project. The existing project didn't have either of these defined, nor does a new project created in Xcode 14. Seems like it might be an Xcode 14 bug.

I'm also still having the same experience, in Xcode beta 4/iOS 16 beta 4 - the intent works fine through the shortcuts app, but my key phrases are totally ignored by Siri, even when typed EXACTLY as they are defined.

I'm finding that while my intents work when manually triggered through the Shortcuts app, the Siri feature simply isn't working. I can type my exact app intent phrase and it simply doesn't pick it up. In addition, it seems like both the ShortcutsLink and SiriTipView are busted. Both of them display placeholder text. App Intents seem to be very unwell. Given how close to GM we must be, it's pretty disappointing.

Found the answer! https://twitter.com/DoleeYang/status/1555828067049672704?s=20&t=pIZNltvSRbBgSD1yp3gRfw

Did you ever work out a way around this? I'm facing the same problem. It seems like a huge gap in this API.

Yep this is the same error I'm seeing. [quote='790121022, twof, /thread/756681?answerId=790121022#790121022, /profile/twof'] I'm also running into this issue. If I go into the diagnostics for the previews I see that the error is LLVMError(description: "Failed to materialize symbols. I didn't see any other relevant results for this error on Google. [/quote]

What ended up "solving" this for me, was removing all of my third party Swift packages that I imported. It didn't appear to be any particular package that caused it, as removing them one at a time made no difference - it was just the presence of any packages that seemed to upset it.

I'm interested to hear how this worked for you - where is the URL available when the app launches? I've tried different variations of this, and whilst my app launches, I can't work out where the URL ends up?

This seems to be fixed in beta 3.