Skip to content

fix: suppress WASM0001 sqlite3_config/db_config varargs warnings on TodoApp.Uno browserwasm #567

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adrianhall merged 2 commits into from
Jul 11, 2026
Merged

fix: suppress WASM0001 sqlite3_config/db_config varargs warnings on TodoApp.Uno browserwasm #567

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
415cc4f
fix: suppress WASM0001 sqlite3_config/db_config varargs warnings on T…
Jul 11, 2026
1251a0f
Merge branch 'main' into issues/543
adrianhall Jul 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/samples/todoapp/unoplatform.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,14 @@ If you bump into issues at this point, ensure you can properly develop and run U
!!! info Tested platforms
The TodoApp.Uno sample is known to work on Android and Desktop. We have not tested on other platforms.

!!! info WASM0001 warning on the browserwasm head
When building the `browserwasm` head, you may see a `WASM0001` warning about native varargs
functions (`sqlite3_config`/`sqlite3_db_config`) in the bundled SQLite provider. This is
harmless diagnostic noise from the WebAssembly SDK's native-interop check - the sample's
actual SQLite usage never calls those functions directly - and is already suppressed for
this sample's `.csproj`. See the [Blazor WASM support](../../in-depth/client/advanced/blazor-wasm.md#suppress-the-wasm0001-warning)
page for more detail on why this warning occurs and how to suppress it in your own project.

## Deploy a datasync server to Azure

Before you begin adjusting the application for offline usage, you must [deploy a datasync service](./server.md). Make a note of the URI of the service before continuing.
Expand Down
14 changes: 14 additions & 0 deletions samples/todoapp/TodoApp.Uno/TodoApp.Uno/TodoApp.Uno.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,20 @@
$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'maccatalyst'
">$(MSBuildWarningsAsMessages);MT7156</MSBuildWarningsAsMessages>

<!--
e_sqlite3 (bundled via SQLitePCLRaw.bundle_e_sqlite3, pinned for #492) exposes variadic
(varargs) native functions (sqlite3_config/sqlite3_db_config). The WebAssembly SDK's
build-time native-interop check flags every fixed-arity P/Invoke overload SQLitePCLRaw
ships to work around this (sqlite3_config_none, sqlite3_config_int, etc.) as WASM0001,
even though this sample's actual SQLite usage (in-memory EF Core CRUD via AppDbContext)
never calls sqlite3_config/sqlite3_db_config directly. This is diagnostic-only noise -
WASM0001 is a standard MSBuild task warning code (emitted via TaskLoggingHelper.LogWarning
in dotnet/runtime's WasmAppBuilder), so it honors NoWarn like any other build warning.
Same documented, NoWarn-suppressible pattern as
docs/in-depth/client/advanced/blazor-wasm.md. See #543.
-->
<NoWarn Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'browserwasm'">$(NoWarn);WASM0001</NoWarn>

</PropertyGroup>
<ItemGroup>
<None Remove="Assets\AddItem.png" />
Expand Down
Loading