IsVisible doesn't work anymore

[HausBJB]

Description

After updating to Sr1, binding to IsVisible no longer works
iOS & MacOS works

I've asked before and will try again

Since a lot of things no longer work for me with this version, I wanted to know how I can get the penultimate version
Android

iOS

Steps to Reproduce

1.Use Repro https://github.com/HausBJB/MauiApp3.git
2.Run
3.Click to Click me
4. image is not displayed
5. But the text changes

Version with bug

6.0.400 (current)

Last version that worked well

6.0.312

Affected platforms

Android

Affected platform versions

Android 12

Did you find any workaround?

No response

Relevant log output

No response

[enisn]

Some related issues with IsVisible

• Elements in same layout doesn't response IsVisible changes [iOS][Mac] #7482
• iOS Layouts not resizing #7507
• [Bug] IsVisible doesn't work for custom controls which inherits from View #3410

IsVisible property wasn't working well before,

[ederbond]

The same here with the latest version (6.0.400). My whole application is now broken.

[HausBJB]

Yes, and development will probably have to be postponed until the next version comes out

[Giuseppetm]

Same here, this is a huge problem.

[manuelelucchi]

I find disappointing and concerning that this release, after 3 weeks of known bugs, doesn't fix anything important and instead introduces new fatal bugs. In our application we had

• App icons not working correctly (Automatically add MauiIcon to AndroidManifest.xml #8063, Multiple Fixes for Resizetizer (esp. Android App Icons) #8020)
• Modals we can't use because on Android they break when you open the keyboard (Text input of Entry and Editor break modal visualization #7861) and on iOS they broke alerts ([iOS/Catalyst] Fix Alert on modal page #7898)
• Various layout problems that weren't on Forms
  And now IsVisible, that is a really important basic property, doesn't work anymore

And what is annoying the most is that we opened issues and there are even pull requests that fixes them opened since days that no one closed and so they didn't end up in SR1, making us wait WEEKS for them

I really like Xamarin and of course I like Maui more for how many things it improved, but it's really frustrating to develop with it knowing that each new release is going to break more things than it fixes

[jsuarezruiz]

Some related issues with IsVisible

• Elements in same layout doesn't response IsVisible changes [iOS][Mac] #7482
• iOS Layouts not resizing #7507
• [Bug] IsVisible doesn't work for custom controls which inherits from View #3410

IsVisible property wasn't working well before,

I don't think they're related, but I'll check it out. The first two ones will be fixed with #6892

[HausBJB]

Yes, and the comments are now filtered, although no one offended anyone

[jsuarezruiz]

Can reproduce the issue. Is a really critical one. I'm going to try to move it as fast as possible.

[jsuarezruiz]

Initial feedback from a quick review:

• The native property of the control, Visibility, sets the ViewStates correctly (Visible, Gone etc). In fact, this is validated by tests added when the property was implemented:

  maui/src/Core/tests/DeviceTests/Handlers/HandlerTestBase.Tests.cs

  Line 23 in 5a92f6c

  public virtual async Task SetVisibility(Visibility visibility)

  This tests run with each View (Label, Button etc).

• If the value of the bool property that manage the visibility is initially false, this happens:

• If, on the other hand, the bool property that manage the visibility is initially true, this happens:

With the above, I suspect that the problem could be related to Layouts. We need to investigate it more.

[manuelelucchi]

@jsuarezruiz While we wait for the fix, is there a way to regress the maui version? Can we choose the workload version manually? Since maui is not a nuget package...

BTW, how is the plan for maui updates from the GA and going on? One every 2-3 weeks like dotnet stable? isn't it a little too much for a new project that has tons of issue to fix?

Thank you for your work

[jsuarezruiz]

@jsuarezruiz While we wait for the fix, is there a way to regress the maui version? Can we choose the workload version manually? Since maui is not a nuget package...

BTW, how is the plan for maui updates from the GA and going on? One every 2-3 weeks like dotnet stable? isn't it a little too much for a new project that has tons of issue to fix?

Thank you for your work

There is no official documentation to downgrade workloads. The Development Wiki can help you https://github.com/dotnet/maui/blob/main/.github/DEVELOPMENT.md. Sorry for the inconvenience, maybe we can find a workaround for this.

Regarding the pace of releases, yes, will be with dotnet releases.

[manuelelucchi]

@jsuarezruiz While we wait for the fix, is there a way to regress the maui version? Can we choose the workload version manually? Since maui is not a nuget package...

BTW, how is the plan for maui updates from the GA and going on? One every 2-3 weeks like dotnet stable? isn't it a little too much for a new project that has tons of issue to fix?

Thank you for your work

There is no official documentation to downgrade workloads. The Development Wiki can help you https://github.com/dotnet/maui/blob/main/.github/DEVELOPMENT.md. Sorry for the inconvenience, maybe we can find a workaround for this.

Regarding the pace of releases, yes, will be with dotnet releases.

To be honest not being able to choose the workload version seems like a big problem for new projects like Maui that aren't exactly stable

[ederbond]

Come on MSFT, you guys should re-think this strategy to release new versions of MAUI tied to VS/.NET releases.
MAUI is far from stable, in fact it's too buggy at this moment. You guys have released it as GA telling us that it's ready for production but that's so not true, very basic things simply just doesn't work. Look that the number of open issues that you already have on this git repo, and the small number of official team members. I was hopping that MAUI would be better then XF in terms of quality and reliability but it's not, it's worst at this moment.

[Vpatel541]

My application is also broken as IsVisible being set to false initially causes none of my slide menus to function properly

[TwoTicketsPls]

Seeing this on Android 11 & 12. Using Microsoft Visual Studio Community 2022 (64-bit) - Preview Version 17.3.0 Preview 2.0.

All good if bound property is initially set to true. Otherwise not.

Edit: But not binding related apparently, as setting IsVisible manually in code behind gives the same results.

[ajphall]

For those struggling to work around this, there are some instructions here https://github.com/dotnet/maui/blob/main/.github/DEVELOPMENT.md that kind of explain how to get a nightly build. However, I found they were quite confusing and incomplete. If you want to try a nightly build here is what I did.

Run the command found on the DEVELOPMENT.md page:

dotnet workload install maui --from-rollback-file https://aka.ms/dotnet/maui/net6.0.json --source https://pkgs.dev.azure.com/dnceng/public/_packaging/darc-pub-dotnet-runtime-a21b9a2d/nuget/v3/index.json --source https://pkgs.dev.azure.com/dnceng/public/_packaging/darc-pub-dotnet-emsdk-52e9452f-3/nuget/v3/index.json --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json --source https://api.nuget.org/v3/index.json --include-previews

(I added the --include-previews I'm not sure if this is necessary)

This seems to install the latest nightly build version of the workload

Open the file https://aka.ms/dotnet/maui/net6.0.json in your browser. There is a line: "microsoft.net.sdk.maui": "6.0.500-preview.1.6059/6.0.300",

Now go into your csproj files and add the version number from the net6.0.json file in a PropertyGroup, e.g.:

<MauiVersion>6.0.500-preview.1.6059</MauiVersion>

Now IsVisible is working again.

Hopefully that helps people out - good luck..

[HobDev]

This issue could be related.

[fabio-popup]

Same issue here :( my whole app is broken now.

[yousufctec]

This bug made me think choosing .NET MAUI at this earlier stage is a blunt mistake. We wasted few man-days on this.

[8m0]

We were able to work around and continue development by setting the Height property of a Grid.RowDefinition to 0 initially, and then toggling to the desired height to show the contained controls. Haven't checked to see if this 'Height hack' will work with other controls, but at least we are able to keep developing until this IsVisible issue gets resolved.

With rowdef children inside of a grid is visible, so you need to hide them as well which is a bumer, especially if you want to DRY.

[fabio-popup]

Just for now, in order to work, I setted <MauiVersion>6.0.312</MauiVersion> in project and eventually installed workloads with dotnet workload restore
Obviously with these solution the problem doesn't use a prerelease and opfully it's more stable.
Hope this can help someone else

[Schinwinkwinsky]

Just for now, in order to work, I setted <MauiVersion>6.0.312</MauiVersion> in project and eventually installed workloads with dotnet workload restore Obviously with these solution the problem doesn't use a prerelease and opfully it's more stable. Hope this can help someone else

I was confusing the Maui version with Dotnet version. I was setting <MauiVersion>6.0.301</MauiVersion> that's the last stable Dotnet version on my machine.

But what we can consider is the Maui version and I don't know why the default on VS 2022 Preview is 6.0.500-preview.1.6059.

If we look for "Maui.Core" on nuget we can find some stable versions.

I set <MauiVersion>6.0.400</MauiVersion> and the last issues I've faced were gone. I'll wait for next stable version.

[SpaaJ]

After 2 days of search .. the trick call Arrange() after IsVisible modifications:

Exemple :

public async Task StartFaceAnimation()
    {
        Dispatcher.Dispatch(() =>
        {
            FaceNormal.IsVisible = true;
            FaceLoose.IsVisible = false;
            Arrange(new Rect());
        });
        await Task.Delay(2000);
        Dispatcher.Dispatch(() =>
        {
            FaceNormal.IsVisible = false;
            FaceLoose.IsVisible = true;
            Arrange(new Rect());
        });
    }

It redraws the controls !

[8m0]

After 2 days of search .. the trick call Arrange() after IsVisible modifications:

Exemple :

public async Task StartFaceAnimation()
    {
        Dispatcher.Dispatch(() =>
        {
            FaceNormal.IsVisible = true;
            FaceLoose.IsVisible = false;
            Arrange(new Rect());
        });
        await Task.Delay(2000);
        Dispatcher.Dispatch(() =>
        {
            FaceNormal.IsVisible = false;
            FaceLoose.IsVisible = true;
            Arrange(new Rect());
        });
    }

It redraws the controls !

2 days Carl.... :) .... of random methods cycle :)

[mobilewares]

Hey @ajphall (or others) :

I used your technique above last week and it was working/ I was able to run my App :

For those struggling to work around this, there are some instructions here https://github.com/dotnet/maui/blob/main/.github/DEVELOPMENT.md that kind of explain how to get a nightly build. However, I found they were quite confusing and incomplete. If you want to try a nightly build here is what I did.

Run the command found on the DEVELOPMENT.md page:

dotnet workload install maui --from-rollback-file https://aka.ms/dotnet/maui/net6.0.json --source https://pkgs.dev.azure.com/dnceng/public/_packaging/darc-pub-dotnet-runtime-a21b9a2d/nuget/v3/index.json --source https://pkgs.dev.azure.com/dnceng/public/_packaging/darc-pub-dotnet-emsdk-52e9452f-3/nuget/v3/index.json --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json --source https://api.nuget.org/v3/index.json --include-previews

(I added the --include-previews I'm not sure if this is necessary)

This seems to install the latest nightly build version of the workload

Open the file https://aka.ms/dotnet/maui/net6.0.json in your browser. There is a line: "microsoft.net.sdk.maui": "6.0.500-preview.1.6059/6.0.300",

Now go into your csproj files and add the version number from the net6.0.json file in a PropertyGroup, e.g.:

<MauiVersion>6.0.500-preview.1.6059</MauiVersion>

Now IsVisible is working again.

Hopefully that helps people out - good luck..

Then, I (foolishly) decided to try and grab an updated nightly build using same technique a couple of days ago (and again today) :

• Deleted my bin/obj folders
• ran the dotnet workload install command above
• grabbed the latest maui version number from that URL (which is currently '6.0.500-preview.1.6118') and updated the MauVersion in my .csproj file as I did before..

Now when I load the solution and try to compile it I'm getting the error (one of therse for each target) :

Assets file '\obj\project.assets.json' doesn't have a target for 'net6.0-android'. Ensure that restore has run and that you have included 'net6.0-android' in the TargetFrameworks for your project.

And I've not been able to get past this since.. (retried this last 3 days with nightly build numbers) and keep getting same error. I also tried the 'dotnet nuget locals all --clear' command from that Developement.md doc just in case that would help plus trying to do dotnet workload restore variations.

Any ideas on how to get back to scenario where I can compile/run my app from the latest nightly build again?

thanks in advance if any ideas?

[victorsigga]

i'm still with this problem, when trying to set a button to false, don't work, but when trying to set an entry, it works fine.

[fabio-popup]

i'm still with this problem, when trying to set a button to false, don't work, but when trying to set an entry, it works fine.

In last VS 2022 Preview ( Version 17.3.0 Preview 4.0) this is fixed.

[victorsigga]

i'm still with this problem, when trying to set a button to false, don't work, but when trying to set an entry, it works fine.

In last VS 2022 Preview ( Version 17.3.0 Preview 4.0) this is fixed.

@fabio-popup i'm 5.0 and the issue still occurs. have you tested in windows ?