Skip to content

[Android] Fix WebView.CanGoBack() returning true on first navigated page due to synthetic about:blank history entry - #35841

Merged
kubaflo merged 4 commits into
dotnet:inflight/currentfrom
praveenkumarkarunanithi:fix-35788
Jun 19, 2026
Merged

kubaflo merged 4 commits into
dotnet:inflight/currentfrom
praveenkumarkarunanithi:fix-35788

fix update as per internal concerns

29bf655
Select commit
Loading
Failed to load commit list.
Azure Pipelines / maui-pr-devicetests failed Jun 19, 2026 in 1h 22m 1s

Build #10.0.90-ci+pr.35841.azdo.1472099 had test failures

Details

Tests

  • Failed: 56 (1.20%)
  • Passed: 4,438 (94.83%)
  • Other: 186 (3.97%)
  • Total: 4,680

Annotations

Check failure on line 581 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

Build log #L581

Cmd.exe exited with code '1'.

Check failure on line 1107 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

Build log #L1107

Cmd.exe exited with code '1'.

Check failure on line 58 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

Build log #L58

PowerShell exited with code '1'.

Check failure on line 54 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

Build log #L54

PowerShell exited with code '1'.

Check failure on line 1 in RequestsCanBeInterceptedAndCustomDataReturnedForDifferentHosts(uriBase: \"https://echo.free.beeceptor.com/sample-request\")

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

RequestsCanBeInterceptedAndCustomDataReturnedForDifferentHosts(uriBase: \"https://echo.free.beeceptor.com/sample-request\")

Assert.Equal() Failure: Strings differ
           ↓ (pos 0)
Expected: "Hello Matthew (param1=value1, param2=valu"···
Actual:   "Failed to fetch"
           ↑ (pos 0)
Raw output
   at Microsoft.Maui.MauiBlazorWebView.DeviceTests.Elements.BlazorWebViewTests.<>c__DisplayClass24_0.<<RequestsCanBeInterceptedAndCustomDataReturnedForDifferentHosts>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Maui.MauiBlazorWebView.DeviceTests.Elements.BlazorWebViewTests.<>c__DisplayClass28_0.<<RunTest>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Maui.DeviceTests.HandlerTestBasement.<>c__DisplayClass20_0.<<AttachAndRun>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Maui.DeviceTests.AssertionExtensions.<AttachAndRun>g__Run|21_0[T](View view, Func`1 action)
   at Microsoft.Maui.DeviceTests.AssertionExtensions.AttachAndRun[T](View view, Func`1 action)
   at Microsoft.Maui.DeviceTests.AssertionExtensions.<>c__DisplayClass72_0`2.<<AttachAndRun>g__Run|0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Maui.Dispatching.DispatcherExtensions.<>c__DisplayClass2_0`1.<<DispatchAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Maui.MauiBlazorWebView.DeviceTests.Elements.BlazorWebViewTests.RunTest(Func`3 test)
--- End of stack trace from previous location ---

Check failure on line 1 in ReturnType Initializes Correctly

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

ReturnType Initializes Correctly

Test failed

Check failure on line 1 in com.microsoft.maui.controls.devicetests-Signed.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

com.microsoft.maui.controls.devicetests-Signed.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

Check failure on line 1 in com.microsoft.maui.core.devicetests-Signed.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

com.microsoft.maui.core.devicetests-Signed.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.