I have setup a custom intent and it all seems to be working fine except that the handler is not being called. Siri responds as if everything was successful but I don't see anything in the console output and none of my breakpoints are triggering... Here is the handler...@implementation IntentHandler - (id)handlerForIntent:(INIntent *)intent { // This is the default implementation. If you want different objects to handle different intents, // you can override this and return the handler you want for that particular intent. NSLog(@"In handlerForIntent."); if ([intent isKindOfClass:[TriggerSceneIntent class]]) { return [SceneIntentsHandler sharedInstance]; } return self; } @endI have breakpoints at lines 10, 12, and 15. None of them are being hit. I also never see "In handlerForIntent" in the console log in xCode.I'm guessing this is something fairly simple that I missed but I'm not seeing it. Welcome any suggestions?

Is there a process to submit a shortcut to Apple for approval? Perhaps so that it can be added it to the gallery? At the very least so that it is not considered "untrusted". We are looking to do this so that the difficult onboarding of an "untrusted" shortcut can be avoided.

I've found that you can add a Siri Shortcut using the following scheme... shortcuts://create-shortcut However I'd like to pass it parameters to fill in the shortcut so that the user just has to click add/done/accept to add the shortcut to their Shortcuts app. I've tried to find documentation about the URL scheme and if it can be sent any parameters but this is all I have found so far... https://support.apple.com/en-ca/guide/shortcuts/apda283236d7/ios Hoping someone can point me in the right direction.

According to the WWDC video found here... https://developer.apple.com/videos/play/wwdc2020/10676 At 22:00 the discussion around Private Wi-Fi is addressed. From a traveller's perspective this could cause some headaches having to re-login to a hotel's wifi every day. For a short term stay this may be acceptable but for long term stays, a week, a month, this could be frustrating. Therefore perhaps an additional switch that disables the 24 hour generation of the private address should also be included. Travellers very much appreciate the security around the mac randomness every time they connect to a new WIFI network. But they may not wish to have to deal with it every day. Therefore it shouldn't be an all or nothing thing. A switch to enable the feature as a whole and a second switch for the 24 hour feature. Thoughts?