Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

4 Commits

Folders and files

Repository files navigation

MudBlazorTestOne

AGENT-CONTROLLED README

Minimal, standalone iOS .NET MAUI Blazor Hybrid application for the supplied MudBlazor slider crash, with App-owned controls for comparison. It has one project, no project references, no backend, no authentication and no theme-preview callbacks. Controls are labelled by implementation.

A crash is reproduced in Debug with Mono AOT enabled. On an Apple Silicon iPhone 14 Pro Max simulator running iOS 26.5, dragging the color picker's hue slider terminated the app. The operator also confirmed the crash. The new native report records EXC_CRASH / SIGABRT on the main thread. Its runtime assertion is:

mini-generic-sharing.c:2761
condition `is_ok (error)' not met, function:mini_instantiate_gshared_info
Attempting to JIT compile method
'void MudBlazor.MudSlider`1/<SetValueTextAsync>d__91<int>:MoveNext ()'
while running in aot-only mode.

The original physical-device Release report has iface_offset != -1; this Debug simulator result has the attempted-JIT assertion above. Both enter the slider's async generic-sharing path. Identical root cause is not established. See the sanitized new crash extract.

Versions

Item Sample
Target net10.0-ios
.NET SDK 10.0.402, exact pin in global.json
Workload set 10.0.402.1
iOS SDK pack 27.1.10018
MAUI workload SDK 10.0.110
MAUI Controls package 10.0.120
MAUI Blazor WebView package 10.0.120
Components / Components.Web, resolved 10.0.14
Components.WebView, resolved 10.0.0
MudBlazor 9.12.0
.NET runtime in built runtimeconfig 10.0.13

The supplied report records a repository SDK pin of 10.0.403, but explicitly does not establish the SDK actually used for its archive. This sample uses the installed 10.0.402 for its verified Debug-AOT build. The MAUI workload SDK version and the explicit MAUI NuGet package versions are separate facts.

AOT in Debug

The project explicitly sets the following for iOS, including Debug:

<PublishAot>false</PublishAot>
<UseInterpreter>false</UseInterpreter>
<MtouchInterpreter></MtouchInterpreter>
<MtouchUseLlvm>false</MtouchUseLlvm>
<MtouchLink>SdkOnly</MtouchLink>
<Optimize>false</Optimize>

This selects Mono AOT on ios-arm64 and iossimulator-arm64. The iOS SDK selects AOT for these architectures even in Debug. PublishAot=true would select the different NativeAOT deployment path. No interpreter workaround is applied. Hot Reload requires the interpreter, so disable Hot Reload for this baseline and use an ordinary Debug build and launch.

References: Microsoft interpreter documentation and iOS build properties.

Build and run on an Apple Silicon Mac

Use the solution in an iOS-capable IDE, or run these commands from this folder. Install .NET SDK 10.0.402 and the pinned MAUI/iOS workloads when absent:

dotnet workload restore
dotnet build MudSliderHybridRepro.csproj -c Debug -r iossimulator-arm64
xcrun simctl list devices available

Choose a booted simulator UUID from that list:

repro_simulator_id=YOUR_SIMULATOR_UUID
xcrun simctl install "$repro_simulator_id" bin/Debug/net10.0-ios/iossimulator-arm64/MudSliderHybridRepro.app
xcrun simctl launch "$repro_simulator_id" com.example.mudsliderhybridrepro

Simulator builds need no profile; the bundle ID is an example. For a physical iPhone, choose your own bundle ID and development signing identity/profile, then build -c Debug -r ios-arm64 and deploy with your usual iOS tooling. No signing credentials or profiles are supplied.

Compare and reproduce

Page Owned section MudBlazor section
Color pickers AppMudColorPicker, with its own hue/alpha ranges, saturation/brightness plane and HEX field Static MudColorPicker using the original parameters
Sliders Two nongeneric AppMudColorSlider instances Two original MudSlider<int> instances

Owned controls appear first on a phone and on the left on a wide display. Each implementation has separate state: pickers start at #58A6FFFF, and the slider pairs start at hue 180 / alpha 255. Changing one implementation does not change the other implementation's values. Sections are labelled with their exact component names and implementation ownership; each range has a hue/alpha label.

  1. Launch the app and test AppMudColorPicker — Owned: drag hue, alpha and the saturation/brightness plane; edit HEX. Observe its displayed value.
  2. Scroll to MudColorPicker — MudBlazor and drag its rainbow hue slider to exercise the original crash baseline. A native crash ends the entire app.
  3. Relaunch and choose Sliders. Test AppMudColorSlider — Owned, then MudSlider — MudBlazor; each pair displays its own current values.

The comparison pages are Components/Pages/Home.razor and Components/Pages/SliderOnlyRepro.razor. Prior baseline: sanitized crash. Current comparison verification follows.

Owned component sources and assets

The standalone copies live in Components/Owned. Their native-range input, HSV/HEX conversion, pointer capture, pending-input coalescing and disposal behavior come from the App-owned implementation. The standalone adaptations change the C# namespace, add explicit imports (including the Blazor focus-event alias), and replace App resource lookup with fixed English demo labels. The demo does not import the App's resource system or projects.

TypeScript and Sass sources are included along with their generated JS/CSS. Ordinary dotnet build uses the checked-in assets and requires no Node tooling. After changing the owned TypeScript or Sass, regenerate with:

npm ci --ignore-scripts
npm run build:assets

The lockfile pins TypeScript 5.9.2 and Sass 1.93.1. Edit the .ts / .scss sources and regenerate; do not edit wwwroot/owned-controls.js or .css directly.

Current matched runtime matrices

The operator's original paired int-slider drag at12:20:49UTC produced a matched SIGABRT through SetValueTextAsync; owned input updated without exit. The controlled Debug /matched-sliders ladder changes one dimension at a time:

Case, initial180/range0..360/step1/Immediate Full-AOT Debug all,-MudBlazor Debug
int plain bind, no label SIGABRT four values updated
double plain bind, no label SIGABRT four values updated
double explicit Task callback, no label SIGABRT four values updated
Blade exact double callback/ValueLabel SIGABRT four values updated

These later inputs are synthetic actual DOM events, with .NET outputs checked. The two Debug modes emit FULL vs INTERP. See the slider evidence. The Debug dropdown matrix separately passed 10 runs,32 popup selections/rerenders and10 remount cycles in those modes.

Release differs: a four-cell experiment varies all,-MudBlazor vs all and SdkOnly/partial vs None/copy. Both mixed cells crash during stock-select mount; both all cells pass all dropdown interactions. None alone did not avoid the mixed fault. The two exact slider variants then pass8/8 runs in the same frozen Release artifacts (32 checked values). See Release policy/link matrix and #6558 evaluation. No physical or universal runtime-fix claim follows from these simulator results.

Original baseline verification and scope

  • Debug iossimulator-arm64 build passed with zero errors; two local Xcode preferences deprecation warnings remained.
  • Effective _ComputeVariables values were UseMonoRuntime=true, _RunAotCompiler=true, UseInterpreter=false, empty MtouchInterpreter, PublishAot=false, MtouchUseLlvm=false, TrimMode=partial, Optimize=false.
  • SDK outputs include MudBlazor.dll.o and packaged MudBlazor.aotdata.arm64.
  • The installed sample rendered its initial color correctly and crashed during the hue-slider gesture. The new report's frames include MudSlider<T_GSHAREDVT>.SetValueTextAsync and async builder GSHAREDVT frames.
  • Physical-device Debug, Release/TestFlight, alpha-only, slider-only and tablet/rotation checks were not run. Android and Windows are outside this deliberately iOS-only sample.

Empty local Directory.Build.props and Directory.Build.targets keep the sample independent of parent build imports when cloned inside another checkout. NuGet.Config supplies only nuget.org. This repository contains the source and a sanitized crash extract. Build outputs, signing material, raw crash reports and local logs are excluded from version control.

Isolated selector and slider cases

Open 647 selector tests to test the stock string select with the three option-registration shapes from the failing Blade theme page: static mode items, generated SYSTEM/USER template items, and color roles with a swatch. The page initially mounts only an HTML chooser. Run all three or select an individual case; native HTML select is the control. Direct diagnostic paths end in /select-only-repro/all, /mode, /template, /role or /native under the same /select-only-repro/ prefix. Use Matched sliders for the controlled integer/double and binding variants. The simulator and repository are named MudBlazorTestOne. The application bundle and assembly keep their original identities so prior crash reports remain comparable.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages