iOS Release builds stopped working after last update

[AbstractionsAs]

Description

App crashes immediatly with XamlParseException "Cannot assign property "Property": Property does not exist, or is not assignable, or mismatching type between value and property (XamlParseException)".

This seems to be caused by style setters?
Works fine in debug, also works fine for all builds on Android.

Steps to Reproduce

It seems like this has to do with style setters beeing removed by the linker. It happens immeiatly when I launch the app.

Link to public reproduction project repository

None

Version with bug

7.0 (current)

Last version that worked well

7.0 (current)

Affected platforms

iOS

Affected platform versions

iOS 16.2

Did you find any workaround?

No response

Relevant log output

XamlParseException "Cannot assign property "Property": Property does not exist, or is not assignable, or mismatching type between value and property (XamlParseException)".

Hi @AbstractionsAs. We have added the "s/needs-repro" label to this issue, which indicates that we require steps and sample code to reproduce the issue before we can take further action. Please try to create a minimal sample project/solution or code samples which reproduce the issue, ideally as a GitHub repo that we can clone. See more details about creating repros here: https://github.com/dotnet/maui/blob/main/.github/repro.md

This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[AbstractionsAs]

I'm expremely pressed for time, and I don't know if I can do this in the timeframe required. Meanwhile, I'm deploying debug builds to the AppStore, while looking into a way to use an older version of Maui in my iOS pipeline.

There's a number of serious bugs I've simply skipped reporting because of this open-repo requirement. It's too much work I don't have time for, and it doesn't really feel like the team takes bug reports seriously anyway.

Maui is not production-ready (unfortunaly for me, given that I'm developing a major project using it).

[breenbob]

This has started to affect us in one of our major ongoing Maui projects also after a VS update. Disabling linker will get us away for now, but we can't go to production until this issue is fixed... Would be good to see some priority given to this.

From looking at line numbers in the exception, assuming it relates to Xaml, I think it is occurring for us in a Data Trigger on a Button Text Property:

<Button Command="{Binding NextCommand}"
      Text="Next">
      <Button.Triggers>
          <DataTrigger
              Binding="{Binding IsSubmitBusy}"
              TargetType="Button"
              Value="True">
              <!-- Exception happening on this line -->
              <Setter Property="Text" Value="" />
          </DataTrigger>
      </Button.Triggers>
  </Button>

[breenbob]

Actually it seems disabling linker on iOS Release builds does not resolve this issue, making this is a much more serious issue. But positively removing our DataTrigger does prevent the crash, so hopefully a pointer in what to test for a repro and fix.

[jsuarezruiz]

@rolfbjarne Thoughts?

[rolfbjarne]

One idea might be to enable the interpreter on a Release build, and see if that changes anything:

<PropertyGroup>
    <UseInterpreter>true</UseInterpreter>
</PropertyGroup>

[breenbob]

Thanks @rolfbjarne. Will give it a go and add an update.