Including a NativeFileReference causes a Blazor error in Release mode

[genifycom]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Create a default Blazor WebAssembly App project. Configure for HTTPS only.

This project runs successfully in both Debug and Release mode.

Now add a Folder Data and place in there the e_sqlite3.o file from Steve Sandersons demo.

Add to the Project file the line in Item Group

<NativeFileReference Include="Data\e_sqlite3.o" />

Now the project will run in Debug mode, but in Release mode it gets an error as follows:

blazor.webassembly.js:1 Assertion failed: Cannot call unknown function mono_wasm_set_is_debugger_attached, make sure it is exported

This means that we cannot use Hot Release (currently only runs in Release mode) with a native file.

Expected Behavior

Native Files should be useable in both Debug and Release mode.

Steps To Reproduce

Described above

Exceptions (if any)

blazor.webassembly.js:1 Assertion failed: Cannot call unknown function mono_wasm_set_is_debugger_attached, make sure it is exported

.NET Version

Net 6.0

Anything else?

.NET SDK (reflecting any global.json):
Version: 6.0.101
Commit: ef49f6213a

Runtime Environment:
OS Name: Windows
OS Version: 10.0.19043
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\6.0.101\

Host (useful for support):
Version: 6.0.1
Commit: 3a25a7f1cc

.NET SDKs installed:
3.1.406 [C:\Program Files\dotnet\sdk]
5.0.103 [C:\Program Files\dotnet\sdk]
5.0.202 [C:\Program Files\dotnet\sdk]
5.0.300 [C:\Program Files\dotnet\sdk]
5.0.301 [C:\Program Files\dotnet\sdk]
6.0.100 [C:\Program Files\dotnet\sdk]
6.0.101 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 3.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.12 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Microsoft Visual Studio Community 2022 (64-bit)
Version 17.0.5

[genifycom]

I did try <PublishTrimmed>false</PublishTrimmed> but the behavior did not change.

[genifycom]

I also tried -s ERROR_ON_UNDEFINED_SYMBOLS=0 in emcc-default.rsp as per issue #39528

[javiercn]

@genifycom thanks for contacting us.

@SteveSandersonMS do you have any thoughts?

[SteveSandersonMS]

I definitely published the BlazeOrbital demo and verified it works, both with and without AOT compilation, since I was collecting stats on the resulting app size - these numbers were in one of the presentation slides. I didn't encounter any such error.

@genifycom Perhaps there is some configuration difference between your app and the BlazeOrbital demo app. If you can provide a minimal repro case for the fault you're seeing (as a GitHub repo), we'd be able to investigate.

[SteveSandersonMS]

I also tried following the repro steps exactly as given above, on .NET 6.0.1, and didn't encounter any error.

Hi @genifycom. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. 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.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.

[fingers10]

@SteveSandersonMS Here is a sample repo using Sqlite and EFCore and this errors out when publishing the blazor wasm app. Please can you assist?