Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

MvxMasterDetailPage doesn't work on UWP #4311

Open
1 of 7 tasks
Antonio2103 opened this issue Oct 29, 2021 · 13 comments
Open
1 of 7 tasks

MvxMasterDetailPage doesn't work on UWP #4311

Antonio2103 opened this issue Oct 29, 2021 · 13 comments
Labels
s/needs-more-info Needs more information from the reporter

Comments

@Antonio2103
Copy link

馃悰 Bug Report

After migrated to Mvx 8.0.2 from Mvx 7.1.2, MvxMasterDetailPage doesn't work properly on UWP, in fact, master page (menu) is blank. No issue on IOS and Android

Expected behavior

Master Page should be visible.

Reproduction steps

Create a new project with MvxMasterDetailPage with some element in menu page.

Configuration

No particular configuration is needed

Version: 8.0.2

Platform:

  • 馃摫 iOS
  • 馃 Android
  • 馃弫 WPF
  • 馃寧 UWP
  • 馃崕 MacOS
  • 馃摵 tvOS
  • 馃悞 Xamarin.Forms
@pwisk
Copy link

pwisk commented Nov 8, 2021

I have the same problem in my app in a UWP project.

@MvvmCross MvvmCross deleted a comment from levi930 Nov 11, 2021
@ccanbek89
Copy link

Currently experiencing the same issue.

@gerfen
Copy link

gerfen commented Nov 29, 2021

I have the same issue. I've cloned a demo app to demonstrate the issue. The working code based on MvvmCross 6.2.2 7.1.2 is here. The broken code based on MvvmCross 8.0.2 is here

UPDATE: I rev'd the MvvmCross nuget packages from 6.2.2 to 7.1.2.

@gerfen
Copy link

gerfen commented Dec 6, 2021

If someone can point me in the right direction on how to address this issue, I can work on a PR. At the moment I'm not familiar enough with MvvMCross to know where to start. I can see the UI elements for the MasterDetailPage are rendered but they are not associated to the flyout as shown in the images below.

image

image

@Antonio2103
Copy link
Author

If someone can point me in the right direction on how to address this issue, I can work on a PR. At the moment I'm not familiar enough with MvvMCross to know where to start. I can see the UI elements for the MasterDetailPage are rendered but they are not associated to the flyout as shown in the images below.

image

image

Hi, the issue is not resolved and I don't know any workaround.

@Antonio2103
Copy link
Author

MvvmCross, any idea?
Thanks

@levi930

This comment was marked as off-topic.

@Cheesebaron
Copy link
Member

It is unclear from the description what you are doing. Provide a minimal repro sample and I can have a look.

@Cheesebaron Cheesebaron added the s/needs-more-info Needs more information from the reporter label Jan 31, 2022
@Antonio2103
Copy link
Author

Hi @Cheesebaron

I attached an example project.
As you can see, in a master detail app no menu elements are visible on UWP platform. In this example I expect application show "Home" and "Contacts" opening menu tapping/clicking on hamburger menu. On IOS and Android it works, but not in UWP

So, on IOS (Android is the same):
Simulator Screen Shot - iPhone 12 Pro - 2022-02-01 at 15 17 07

On UWP blank menu instead:
Screenshot 2022-02-01 at 15 18 53

MasterDetailExample.zip

Thank you

@Antonio2103
Copy link
Author

Sorry, wrong UWP screenshot on previous post
Screenshot 2022-02-01 at 15 34 01

@Antonio2103
Copy link
Author

Hi, I cannot update to mvvmcross 8.0.2 until this issue persists. There are any news about it?
Thanks

@MvvmCross MvvmCross deleted a comment from levi930 Feb 28, 2022
@MvvmCross MvvmCross deleted a comment from levi930 Feb 28, 2022
@Antonio2103
Copy link
Author

So, no solution for this issue?
Thanks

@Cheesebaron
Copy link
Member

No, been focusing on other stuff. If you want this resolved quicker. Create a PR and fix it yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s/needs-more-info Needs more information from the reporter
Development

No branches or pull requests

6 participants