Open edgiardina opened 1 year ago
Just following up, this hasn't been categorized, or reviewed, or even put on the backlog.
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
Looks like the provider isn't being set in maui. I was able to address this by adding the code originally found in the Forms.Init to my App.cs
#if IOS
(Application.Current as IApplicationController)?.SetAppIndexingProvider(new IOSAppIndexingProvider());
#endif
Similar may also need to be done for Android.
https://github.com/search?q=repo%3Adotnet%2Fmaui%20SetAppIndexingProvider&type=code
I also think it needs things from the Compat namespace, so in MauiProgram.cs
:
public static MauiApp CreateMauiApp()
{
var builder = MauiApp.CreateBuilder();
builder
.UseMauiCompatibility()
.UseMauiApp<App>();
return builder.Build();
}
Upgraded Xamarin.Forms sample of DeepLinking. For me right now I'm not getting the iOS links that have been registered to appear in the spotlight search.
Verified this issue with Visual Studio Enterprise 17.7.0 Preview 2.0. Can repro on iOS platform with sample project. MauiBugAppLinks.zip
Description
In Xamarin Forms, Using the AppLinks nuget package was straightforward in iOS and required no initialization.
In .NET MAUI, on iOS, AppLinks is built in, but throws an initialization error. It isn't clear from the documentation how to resolve this. This is the case whether an Entitlements.plist declaration is given or not.
Steps to Reproduce
Link to public reproduction project repository
https://github.com/edgiardina/MauiBug_AppLinks_NoIAppIndexing
Version with bug
7.0 (current)
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
iOS 16.1 (but appears to affect all iOS versions)
Did you find any workaround?
No response
Relevant log output
No response