MAUI ios app not working/crashing after deployed to Testflight

[DharunAR]

Description

We have migrated our project from Xamarin to MAUI.

The MAUI ios app is working with release mode in simulator and when archived it with Ad-hoc or published with TestFlight, the app not working properly and it crashes.

Steps to Reproduce

1. Create a MAUI ios project with NET 7
2. My visual studio settings:
   
3. Run the ios app with release mode dotnet build --configuration Release -t:Run -f net7.0-ios -p:_DeviceName=:v2:udid=E4EDAC1E-18DA-4863-920B-098F643B25CB - it is working as expected
4. Deploy to testFlight or archive as an ipa file and try to install on your physical device the app is crashing/ not working properly.

Link to public reproduction project repository

No response

Version with bug

7.0.49

Is this a regression from previous behavior?

Yes, this used to work in Xamarin.Forms

Last version that worked well

Unknown/Other

Affected platforms

iOS

Affected platform versions

ios 16, 17

Did you find any workaround?

#9597 Similar issue were created here and tried adding the workaround
true
in the csproj file but doesn't helped.

Relevant log output

No response

[ghost]

Hi @DharunAR. 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.

[drasticactions]

I believe this isn't an issue with MAUI in general (as in, if you create a new template app, create a release build, archive it, and deploy it, it works fine for me). It's most likely something specific with your application, and with a reproduction of the issue or any more information, this will be possible to debug.

The "workaround" you mentioned was turning on the Mono Interpreter, which most likely worked for that other person because of whatever code or libraries they happened to have brought in.

[DharunAR]

The issue can be closed. Deleting the 'obj' and 'bin' folders and applying the workaround adding Interpreter to "true" helped resolve the problem.