Post not yet marked as solved
I filed FB9045442 about this, and now Feedback Assistant says "Resolution: Potential fix identified - In iOS 15".
Post not yet marked as solved
Yes, we are seeing the same problem after app updates. Many of our users have to restart their devices to see our extension. These problems have been going on since iOS 14.0 was released. They never happened on iOS 13.x. I have filed FB8889913 and FB9045442 and have been hoping with each 14.x release that it will be fixed, but it still happens on 14.4.1.
Post not yet marked as solved
I found a way to consistently reproduce this on iOS 14.4.1. If I go to a certain URL (which I would post, but the developer forum software will not allow it), then my sharing action in Safari doesn't show up the first time you open the share sheet, but does show up the second time you open it. This URL has an anchor on the end of it (i.e., it ends with a hash symbol followed by some text).
If I got to the same URL with the anchor removed from the end of it, my sharing action shows up the first time I open the share sheet.
I have filed FB8889913.
Post not yet marked as solved
The Extensions tab of Safari preferences is an absolute clown show. In previous versions of macOS, there have been bugs where it is possible to enable an extension via the keyboard, but the mouse does not work. (See apple dot stackexchange dot com question 214760, because these forums won't allow me to include a link.)
Now the "solution" to this problem on Catalina is to "Make sure that your extension preferences pane is frontmost in the middle of your screen with no other windows covering any of it."
This is ridiculous. Can someone from Apple please explain why it is necessary to have a bunch of hacks that *do not work* in the Safari extension preferences? What exactly is being defended against here, and how is it worth these bizarre bugs that cause our customers to just assume that Safari and our extensions are broken?
Post not yet marked as solved
The only real documentation on this is buried in a WWDC19 video, because Apple can't be bothered to provide decent canonical documentation:
https://developer.apple.com/videos/play/wwdc2019/717/
Please see my response below... Apple responded to me in Feedback Assistant and I have it working now!
Apple responded to me in Feedback Assistant and I have it working now!!Here is what they said:"Does your app have localizations? Are you testing in a locale different than English? Make sure that CFBundleDevelopmentRegion of your app matches Siri language or localize your intent definition file into languages supported by Siri."This helped me track it down.The CFBundleDevelopmentRegion of my app target was set to "English". This is a project that has been around for a long time, so it still had an old-style localization name in there. At some point in the last few years, Apple changed the way you're supposed to specify localization names from "English", "French", etc. to "en", "fr-FR", etc. The CFBundleDevelopmentRegion of my other targets was set to "en" in some cases and "$(DEVELOPMENT_LANGUAGE)" in others. (My development language is English.) Changing the CFBundleDevelopmentRegion of my app target from "English" to "en" fixed it, and I started to get the correct conversational prompts from Siri!Now, of course, if things are broken in this case, then I think Xcode should warn you to update your project settings to get rid of old-style localization names. Also, I was getting the correct conversational prompts from Siri during the early iOS 13.0 betas, so it seems like something did change on the SDK side of things.But in any case, it is working for me now. Let me know if this helps you!
It seems pretty likely that it's a bug in iOS. I filed a ticket in Feedback Assistant about it. FB7294261. The question is, will it be fixed in iOS 13.2, 13.3. 13.4, or ...?
I am experiencing the same issue with my app. No matter what I do, Siri will not use my custom voice prompt, and just says, "What should <variablename> be?"I created a test project with an identical Intent definition file, and the custom voice prompt *does* get used in the test project. I've tried to make the test project and my actual project match each other as closely as possible, but no matter what I do, the test project works and my actual project will not work. I've even gone so far as to copy the Intent definition file from one project to another, so the Intent definition file is *exactly* the same across the 2 projects.I'm really at my wits' end on this one. Please let me know if you discover any solution, and I will do the same.
