Severe Bug: Crash when using StoreServicesFeedbackLauncher to lauch Feedback Hub
Calling StoreServicesFeedbackLauncher.LaunchAsync() in a UWP app now causes an unhandled Win32 exception if the target platform is set to Windows 10 version 1809. See https://stackoverflow.com/questions/52769958/microsofts-feedback-hub-now-crashes-my-uwp-app for another report of this.
This means that the Feedback Hub can't be used by apps targeting Windows 10 version 1809 or later.
I have installed the Store Services SDK using the NuGet package method as described here https://docs.microsoft.com/en-gb/windows/uwp/monetize/microsoft-store-services-sdk#install-the-sdk.
A workaround or fix would be appreciated.
A change was made in the Windows core platform where the feedback hub with app context count not launch from a non-UI thread, sadly, the engagement SDK was not updated to support this change. We have updated the SDK to call the launch of the feedback hub from calling thread, we have tested extensively to ensure that it works in the most common scenarios and have updated the SDK (both the MSI and the NuGet) to support this change. If your application is in the Microsoft Store, the application was updated automatically to your end users.
Matt Lacey commented
It seems this issue has returned as it's not working in 1903 with apps distributed via the store.
It works with apps built locally, but when distributed through the store, calling `Microsoft.Services.Store.Engagement.StoreServicesFeedbackLauncher.IsSupported()` causes the app to crash with a MissingMethodException (stowed_exception_system.missingmethodexception 80131513: stowed_exception_system.missingmethodexception)
Carlo Mendoza commented
Seems this was fixed in Microsoft.Services.Store.Engagement 10.1901.28001
Ben Stevens commented
Based on the info in one of the posts on StackOverflow, I've worked out how to launch the Feedback Hub on the page for the current app using an alternative method (still can't provide metadata though). Do this as follows.
await Launcher.LaunchUriAsync(new Uri("feedback-hub://?appid=" + appUserModelId));
where the easiest way I can find to get the appUserModelId is as follows
string appUserModelId = Package.Current.Id.FamilyName + "!" + packageRelativeApplicationId;
where packageRelativeApplicationId is hard-coded in Package.appxmanifest at /Package/Applications/Application@Id and is usually simply App.
Muhammad Touseef commented
same problem here as well
I'm facing this too.
Carlo Mendoza commented
I'm also encountering this bug.