[automated] Merge branch 'main' => 'net11.0'

[github-actions]

I detected changes in the main branch which have not been merged yet to net11.0. I'm a robot and am configured to help you automatically keep net11.0 up to date, so I've opened this PR.

This PR merges commits made on main by the following committers:

• mattleibow
• StephaneDelcroix
• rmarinho
• pictos
• PureWeen

Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.

If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.

Instructions for merging via command line

Run these commands to merge this pull request from the command line.

git fetch
git checkout main
git pull --ff-only
git checkout net11.0
git pull --ff-only
git merge --no-ff main

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet/maui HEAD:merge/main-to-net11.0

or if you are using SSH

git push git@github.com:dotnet/maui HEAD:merge/main-to-net11.0

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/main-to-net11.0'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
The provided examples assume that the remote is named 'origin'. If you have a different remote name, please replace 'origin' with the name of your remote.

git fetch
git checkout -b merge/main-to-net11.0 origin/net11.0
git pull https://github.com/dotnet/maui merge/main-to-net11.0
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/maui HEAD:merge/main-to-net11.0

or if you are using SSH

git fetch
git checkout -b merge/main-to-net11.0 origin/net11.0
git pull git@github.com:dotnet/maui merge/main-to-net11.0
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/maui HEAD:merge/main-to-net11.0

Contact .NET Core Engineering (dotnet/dnceng) if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.

[PureWeen]

/azp run maui-pr-uitests, maui-pr-devicetests

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 34787

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 34787"

[github-actions]

🧪 PR Test Evaluation

Overall Verdict: ✅ Tests are adequate

This is an automated merge PR (main → net11.0) with 69 test files covering the included changes. The test mix leans heavily toward unit and XAML tests (lightest types preferred), with UI tests only where truly needed. Two minor convention issues require attention in the LongPressGestureRecognizer UI tests.

👍 / 👎 — Was this evaluation helpful? React to let us know!

📊 Expand Full Evaluation

PR Test Evaluation Report

PR: #34787 — [automated] Merge branch 'main' => 'net11.0'
Test files evaluated: 69
Fix files: 342

Note: This is an automated merge PR incorporating multiple feature/fix PRs from main. Evaluation focuses on the key new additions: LongPressGestureRecognizer (major new feature), style inheritance fix (#34529), XAML source-gen fixes (#34727), new APIs InvalidateStyle/InvalidateVisualStates (#34723), and XAML warnings (#32654).

---

Overall Verdict

✅ Tests are adequate

The PR includes 38 unit tests, 26 XAML tests, 3 device tests, and 2 UI tests — a well-balanced, lightweight-leaning test suite. The major new feature (LongPressGestureRecognizer) has thorough coverage at multiple levels. Two convention issues need fixing in the UI test.

---

1. Fix Coverage — ✅

The key changes are well covered:

• LongPressGestureRecognizer: LongPressGestureRecognizerTests (20 unit tests) + LongPressGestureRecognizerPerformanceTests (9 tests) cover constructor defaults, Command/CommandParameter, MinimumPressDuration, AllowableMovement, event firing, state transitions, and CanExecute guard. The LongPressGestureInteraction UI test covers tap+longpress independence, swipe-cancels-longpress, longpress-in-scrollview, and multiple simultaneous recognizers.
• Style inheritance fix (Fix style inheritance by unapplying base style before reapplying #34529): StyleTests (56 combined unit tests) and VisualStateManagerTests (24 tests) cover style application/unapplication.
• XAML source-gen x:Key escaping (Fix x:Key values not escaped in source-generated C# string literals #34727): SourceGenXamlCodeBehindTests (15 tests) and BindingRepresentationGenTests (34 tests) cover code generation paths.
• XAML warnings (Add XC0067/MAUIX2015 warning for duplicate implicit content property assignments in XAML #32654): MultipleChildrenWarningTests (4 unit tests) directly targets the new XC0067/MAUIX2015 diagnostic.
• InvalidateStyle/InvalidateVisualStates APIs (Add InvalidateStyle() and VisualStateManager.InvalidateVisualStates() APIs #34723): VisualStateManagerTests + StyleTests cover affected paths.

---

2. Edge Cases & Gaps — ⚠️

Covered:

• LongPress default property values and mutations
• Command execution and CanExecute guard
• LongPress + Tap coexistence (neither blocks the other)
• Swipe cancels LongPress (gesture conflict)
• LongPress inside ScrollView
• Multiple independent LongPress recognizers on same page
• Performance characteristics via LongPressGestureRecognizerPerformanceTests

Missing:

• LongPress on Windows: All Windows UI tests are skipped via Assert.Ignore. No device or unit test validates the Windows handler (LongPressGestureHandler.Windows.cs). A device test for Windows would strengthen coverage.
• LongPress cancellation path (SendLongPressing with cancellation) — the LongPressingEventArgs / in-progress state isn't explicitly tested to verify that cancelling mid-hold suppresses SendLongPressed.
• Flyout memory leak (Fix Flyout memory leak #34485): No dedicated regression test (e.g., a unit test that verifies handler disconnection releases event references) — though this is a common gap for memory-leak fixes.

---

3. Test Type Appropriateness — ✅

Current distribution:

• Unit Tests (38) — property logic, event wiring, XAML binding representation, style application
• XAML Tests (26) — source gen, XamlC, markup extensions
• Device Tests (3) — platform rendering
• UI Tests (2) — gesture interaction flows

Recommendation: Appropriate. The UI tests for LongPressGestureInteraction legitimately need Appium (gesture events can't be tested without a real touch event simulation). The new TapElement extension method in UtilExtensions is correctly factored out as a shared helper.

---

4. Convention Compliance — ⚠️

LongPressGestureInteraction UI test:

• ✅ Inherits _IssuesUITest
• ✅ Has [Category(UITestCategories.Gestures)] on each test method
• ✅ Uses WaitForElement before first interaction in each test
• ❌ Inline #if platform directives (lines 16–21, 29–31, 62–64, 83–85, 100–101): Per guidelines, platform-specific logic must be moved to extension methods for readability. Example fix:

  // In UtilExtensions.cs:
  public static void LongPress(this IApp app, string automationId)
  {
  #if MACCATALYST
      app.LongPress(automationId);
  #else
      app.TouchAndHold(automationId);
  #endif
  }

• ⚠️ LongPress2Label accessed without WaitForElement in LongPressWithSwipe_SwipeCancelsLongPress: The label is always visible on page load so this is low-risk, but adding an explicit wait is more robust.

UtilExtensions — Script flagged as missing _IssuesUITest and [Category], but these are false positives. UtilExtensions is a static utility helper, not a test class. No action needed.

XAML test file naming — Several pre-existing XAML test files use Gh3606, Gh5095, Maui23961 etc. (not zero-padded to 5 digits). These are pre-existing convention deviations not introduced by this PR.

---

5. Flakiness Risk — ⚠️ Medium

• The LongPress UI tests rely on TouchAndHold/LongPress Appium APIs which can be timing-sensitive on slower CI agents. No explicit timeout tuning is present.
• LongPressWithSwipe_SwipeCancelsLongPress uses App.WaitForElement("SwipeLabel") to sync after the swipe, which is good, but gesture-based tests are inherently prone to platform-specific flakiness.
• No Task.Delay or Thread.Sleep misuse detected ✅
• No VerifyScreenshot usage ✅

---

6. Duplicate Coverage — ✅ No duplicates

The LongPressGestureRecognizer is a new API — no pre-existing coverage was displaced. All other test additions complement (not duplicate) existing tests.

---

7. Platform Scope — ⚠️

• Fix files span: Android (25), iOS (47), MacCatalyst (13), Windows (19), cross-platform (250)
• LongPress UI tests run on iOS, Android, MacCatalyst; Windows is explicitly skipped via Assert.Ignore in 3 of 4 tests. The Windows handler (LongPressGestureHandler.Windows.cs) has no automated test path.
• Style/XAML fixes are covered by unit/XAML tests that run on all platforms in CI ✅

---

8. Assertion Quality — ✅

• Unit tests: Specific property equality assertions (e.g., Assert.Equal(200, recognizer.MinimumPressDuration))
• UI tests: Label text assertions verify exact counts (e.g., Assert.That(tapLabel, Is.EqualTo("Tap Count: 1"))) — these will catch regressions in gesture routing
• XAML tests: Diagnostic-level assertions on generated code and compiler output

---

9. Fix-Test Alignment — ✅

• LongPressGestureRecognizer.cs ↔ LongPressGestureRecognizerTests.cs + LongPressGestureInteraction.cs — direct alignment
• StyleTests + VisualStateManagerTests ↔ style inheritance fix — aligned
• MultipleChildrenWarningTests ↔ XC0067 XAML warning fix — direct alignment
• SourceGenXamlCodeBehindTests + BindingRepresentationGenTests ↔ XAML source-gen fixes — aligned

---

Recommendations

1. Fix inline #if directives in LongPressGestureInteraction.cs: Move platform-switching logic into UtilExtensions (e.g., App.PerformLongPress(elementId)) to comply with conventions and improve readability.
2. Add WaitForElement("LongPress2Label") before FindElement("LongPress2Label") in LongPressWithSwipe_SwipeCancelsLongPress — low priority but more robust.
3. Consider a Windows device test for LongPressGestureHandler.Windows.cs — the current Windows-skip via Assert.Ignore leaves the Windows handler untested.
4. Consider a cancellation unit test for LongPressingEventArgs to verify that moving beyond AllowableMovement during a press correctly suppresses the Pressed event.

Warning

⚠️ Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• dc.services.visualstudio.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "dc.services.visualstudio.com"

See Network Configuration for more information.

Note

🔒 Integrity filtering filtered 2 items

Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.

• pr:[automated] Merge branch 'main' => 'net11.0' #34787 (pull_request_read: Resource 'pr:[automated] Merge branch 'main' => 'net11.0' #34787' has lower integrity than agent requires. Agent would need to drop integrity tags [unapproved:all approved:all] to trust this resource.)
• pr:[automated] Merge branch 'main' => 'net11.0' #34787 (pull_request_read: Resource 'pr:[automated] Merge branch 'main' => 'net11.0' #34787' has lower integrity than agent requires. Agent would need to drop integrity tags [approved:all unapproved:all] to trust this resource.)

🧪 Test evaluation by Evaluate PR Tests