You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All Mopups appear to be hidden in the background when called after a FilePicker.
This means the Mopup can't be closed at all so the app itself becomes impossible to interact with.
To the naked eye it looks like the popup just never appears and the app freezes, but if you step through the creation of a popup you can see the popup briefly appear before it is immediately covered by the original calling page.
@Sofiya-kumar Thanks for the suggestion; adding a Task.Delay(100) doesn't seem to work either, though.
I think a change will need to be made to the Mopups code to avoid using a workaround like this anyway.
Description
All Mopups appear to be hidden in the background when called after a FilePicker.
This means the Mopup can't be closed at all so the app itself becomes impossible to interact with.
To the naked eye it looks like the popup just never appears and the app freezes, but if you step through the creation of a popup you can see the popup briefly appear before it is immediately covered by the original calling page.
I've created a sample app that can reproduce the issue: https://github.com/askariya/MauiPopupsApp
I originally noticed this while trying Prism Popups (that utilizes Mopups) and I have a project where it happens in Prism as well: https://github.com/askariya/MauiPrismMopupsSampleApp
Steps to Reproduce
Video:
https://github.com/LuckyDucko/Mopups/assets/15271126/95ada5ac-e43f-4473-97ee-dd9208b62a8b
The text was updated successfully, but these errors were encountered: