microsoft / microsoft/vscode-dotnettools

[BUG] Can't deploy iOS app with Interpreter disabled and Hot Reload enabled

Open
#1,237 6 comments 0 reactions 1 assignee View on GitHub

@BretJohnson is already working on this.

Since Jun 24, 2024.

area-hotreload area-maui bug triaged
Dominant language
No language data
Stars
321
Forks
54
Avg merge
2d 19h
Merged PRs (30d)
2

Description

Describe the Issue

The MAUI Hot Reload assemblies run a source generator that starts a bootstrap process to allow hot reload functions. These functions depend on the Mono Interpreter being enabled. While that is true for MAUI UI apps by default, they are not for .NET iOS apps in general. Unless you disable MAUI Hot Reload, or enable the Mono Interpreter, it will break deployment for .NET iOS apps. Likewise, disabling the interpreter for MAUI UI apps will also blow up deployment.

We need to detect if the interpreter is enabled within the project. if it is, then allow hot reload to start. Else, disable it.

Steps To Reproduce
  1. dotnet new ios
  2. Deploy within the MAUI vscode extension
Expected Behavior

It deploys and runs.

Environment Information

No response

/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/17.2.8053/targets/Xamarin.Shared.Sdk.targets(1215,3): error : Failed to AOT compile aot-instances.dll, the AOT compiler exited with code 139. [/Users/drasticactions/Developer/Work/TestiOSAppClient/TestiOSAppClient.csproj]

ビルドに失敗しました。

/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/17.2.8053/targets/Xamarin.Shared.Sdk.targets(1215,3): error : Failed to AOT compile Microsoft.Maui.Controls.HotReload.Forms.dll, the AOT compiler exited with code 139. [/Users/drasticactions/Developer/Work/TestiOSAppClient/TestiOSAppClient.csproj]
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/17.2.8053/targets/Xamarin.Shared.Sdk.targets(1215,3): error : Failed to AOT compile aot-instances.dll, the AOT compiler exited with code 139. [/Users/drasticactions/Developer/Work/TestiOSAppClient/TestiOSAppClient.csproj]

| VS Bug 2466018

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.