This repository has been archived by the owner on May 1, 2024. It is now read-only.
Xamarin Forms 5 UWP - Issue with Display Alert #14618
Labels
a/alerts
p/UWP
s/needs-info ❓
A question has been asked that requires an answer before work can continue on this issue.
s/needs-repro ❔
This reported issue doesn't include a sample project reproducing the issue. Please provide one.
s/unverified
New report that has yet to be verified
t/bug 🐛
Projects
Description
Hello everyone,
Me and my team have just migrated our cross-platform XF 4 project to XF5.
The only issue that we have encountered thus far is the following:
Our UWP App was throwing an unhandled App.Xaml exception when navigating to a different page for no apparent reason and after some search, installing the nugget Microsoft.UI.Xaml explicitly fixed that issue, even though that nugget package is supposed to be installed along with XF5 nugget.
But right now a new issue has emerged. When calling the 'await Application.Current.MainPage.DisplayAlert(szTitle, szMessage, btnOk, btnCancel);' from the UI thread the alert gets displayed properly but when I click on one of its buttons Ι get an unhandled exception "No installed components were detected. The property path '(controls:AnimatedIcon.State)' could not be resolved for a Setter." where controls is defined as xmlns:controls="using:Microsoft.UI.Xaml.Controls"
Could you please help me find out what is going wrong? As far as I know the DisplayAlert() is handled by Xamarin.Forms.
Steps to Reproduce
It's reproduceable only if, when installing any Xamarin Forms 5 nugget, the Microsoft.UI.Xaml nugget does not get installed as a dependency.
Expected Behavior
The DisplayAlert should work fine and not throw any exception when interacting with the buttons.
Actual Behavior
The DisplayAlert throws an excpetion about missing components, when interacting, that probably are related to the Microsoft.UI.Xaml.Controls nugget.
Basic Information
UWP Target Version: 10.0.19041.0
Xamarin.Forms version: 5.0.0.2083
The text was updated successfully, but these errors were encountered: