Xamarin.forms: [Bug] DisplayPromptAsync not working UWP

[mnxamdev]

Description
DisplayPromptAsync is not working. Nothing happens. I was testing on UWP. I found this issue while working on my own app and looking for a solution I stumbled on #9168 . I've adjusted the sample app to not use Task.Run() and problem still persists.

Steps to Reproduce
Run this project
App1.zip

Click the button.

Nothing happens

Expected Behavior
Prompt dialog should be displayed.

Actual Behavior
Nothing happens

Basic Information
Version with issue: 4.4.0.991477
IDE: 16.4.4

Platform Target Frameworks:
UWP: Windows 10

[bmacombe]

Something broke this since #8720 was merged, I'll take a look

[bmacombe]

it was merged into master...it probably didn't make it into 4.4

[bmacombe]

or 4.5 it looks like

[bmacombe]

yep, these changes are in Master...so looking like 4.6 at this point? @samhouts

At least it's not in 4.5 pre 4 nugets or in the current 4.5 branch it looks like

[samhouts]

Yes, that's right. 4.6. :)

[AndyPresto]

We you sure a fix for this is in 4.6?

I can't see any mention in the release notes

[SymboLinker]

@AndyPresto

We you sure a fix for this is in 4.6?
I can't see any mention in the release notes

I updated Xamarin.Forms from version 4.5.0.65 to 4.6.0.726 and indeed, UWP's DisplayPromptAsync really displays again :)

[webapps-rvcits]

@AndyPresto I beg to disagreed on your statement. The bug on UWP's DisplayPromptAsync is still existing from Xamarin.Forms 4.5.0.356 to 4.6.0.800

[mnxamdev]

We just tested this on Xamarin.Forms 4.6.800 since we are updating to that version today and it seems to be working just fine:

[zgeorgiev]

I just updated package to Xamarin.Forms v.4.6.0.847 and DisplayPromptAsync still not working. I get the following exception:

The text associated with this error code could not be found.

Cannot find a Resource with the Name/Key SystemControlPageBackgroundAltHighBrush [Line: 0 Position: 0]

[MarcinIN]

I have the same error on 4.7.0.1080

[bmacombe]

@zgeorgiev @moqueur I just tested the 6713 issue page (test page for display prompt) on Main, 4.8, 4.7 and 4.6 and can't replicate this issue. I would create a new issue and attach a repro app.