Weekly GitHub Report for Maui

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

Table of Contents

• I. News
  • 1.1. Recent Version Releases
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is 9.0.90

1.2 Version Information:

The .NET MAUI 9.0.90 SR9 release, published on July 11, 2025, includes over 141 commits primarily focused on critical product fixes across iOS, Android, and Windows platforms, testing enhancements, infrastructure updates, and dependency version bumps. Key highlights include numerous bug fixes addressing UI behavior, threading issues, and control improvements, alongside expanded automated testing coverage and housekeeping updates to improve stability and maintainability.

II. Issues

2.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.

1. [T/BUG] [PLATFORM/WINDOWS] [S/VERIFIED] [AREA-CONTROLS-GENERAL] [S/TRIAGED] [PARTNER/SYNCFUSION] [Windows] Declaring a Map in XAML Causes Fault on Page Exit: This issue describes a fault occurring on Windows when a Map control is declared in XAML on a transient page, causing the application to crash upon exiting that page. The problem is reproducible on Windows 11 with .NET MAUI versions 10.0.80 and 10.0.90, and no workaround has been found other than programmatically creating the control only when needed.

   • The comments confirm the issue is reproducible and validated on the specified platform and versions; a proposed fix was tested but did not resolve the fault for the reporter, who suspects environmental differences or a misconfiguration in testing the fix.
   • Number of comments this week: 5

2. [PLATFORM/MACOS] [AREA-TOOLING] [PLATFORM/IOS] [Apple mobile] Debugging: breakpoint never binds on device: This issue describes problems with debugging on Apple mobile devices using CoreCLR, where breakpoints never bind when debugging on an iOS device over USB, and the app fails to install when attempting wireless deployment. The user reports that while the app runs fine and simulator debugging works, breakpoints remain inactive due to missing module-load events, and wireless installation errors indicate connection and transport failures related to device communication.

   • The comments include requests for troubleshooting help, confirmation that the issue is related to USB debugging, updates on partial fixes and ongoing problems, detailed crash logs and root cause analysis involving code-signing failures, and attempts to verify progress with the latest VS Code extensions.
   • Number of comments this week: 2

3. [T/BUG] [PLATFORM/ANDROID] [S/VERIFIED] [AREA-CONTROLS-ACTIVITYINDICATOR] [S/TRIAGED] [I/REGRESSION] [PARTNER/SYNCFUSION] [REGRESSED-IN-10.0.90] Activity indicator stays visible (regression in 10.0.90): This issue describes a regression in version 10.0.90 of .NET MAUI where the ActivityIndicator on Android remains visible and running even after the code sets its IsVisible and IsRunning properties to false, which did not happen in previous versions like 10.0.80. The problem appears to be timing-related and intermittent, with some users confirming it only occurs within certain data loading durations, and a pull request has been submitted and tested to fix the issue.

   • The comments include requests for a reproducible sample, observations about the timing-related nature of the bug, confirmation of the issue in production apps, a proposed workaround involving binding adjustments, a pull request with a fix, and confirmation from the original reporter that the fix resolved the problem on Android.
   • Number of comments this week: 2

4. [AREA-BLAZOR] [S/NEEDS-INFO] [S/VERIFIED] [S/TRIAGED] .NET MAUI Blazor Hybrid shows false PRI263 warning for wwwroot assets: This issue concerns a false PRI263 warning generated in .NET MAUI Blazor Hybrid projects when static web assets located in the wwwroot folder are incorrectly interpreted as culture-dependent resources due to their folder and file naming conventions. The warning arises because the resource indexing tool MakePri.exe mistakenly treats certain wwwroot subfolders and files as language-qualified variants without neutral counterparts, although these assets are served literally by BlazorWebView and do not cause runtime exceptions.

   • The comments confirm the issue is reproducible on Windows with multiple .NET MAUI versions and explain the root cause as MakePri.exe's implicit language qualifier inference on wwwroot assets; suggested workarounds include renaming folders, excluding wwwroot from PRI indexing, or suppressing the warning, while a potential fix involves modifying MAUI's packaging targets to exclude these assets from PRI processing.
   • Number of comments this week: 2

5. [PLATFORM/MACOS] [S/VERIFIED] [S/TRIAGED] [T/A11Y] [PARTNER/SYNCFUSION] VoiceOver does not announce project description when navigating project cards:A11y_.NET MAUI SDKs_VoiceOver: This issue addresses a problem where VoiceOver on Mac does not announce the project description when navigating project cards in the .NET MAUI SDKs sample app, only reading out the project name and role. The expected behavior is for VoiceOver to announce both the project name and its description, which can be fixed by properly structuring the markup with description list elements or by modifying the semantic description using a MultiBinding approach to include both fields.

   • The comments confirm the issue is reproducible on Mac with specific .NET MAUI versions and provide a detailed code example using MultiBinding to combine the project name and description into the accessible semantic description, improving screen reader output.
   • Number of comments this week: 2

2.2 Top 5 Stale Issues:

We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.

As of our latest update, there are no stale issues for the project this week.

2.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 22

Summarized Issues:

• Swipe and Gesture Tracking Issues: The SwipeView control inside a CollectionView stops tracking an active swipe gesture when the user's finger temporarily leaves the item bounds, causing unreliable and less fluid swipe interactions on mobile platforms. This issue affects the user experience by pausing the swipe until the finger re-enters the item area.
• issues/37089

• Memory Management and Leak Problems: The RealParent property on a popup is unexpectedly garbage collected on Windows in version 10.0.90, and a persistent memory leak related to CollectionView occurs when navigating away, linked to dependency injection references. These issues cause regressions and app slowdowns despite other memory leaks being resolved.
• issues/37093, issues/37153

• Windows Platform Crashes and Faults: Declaring a Map control in XAML on a transient page causes a crash on Windows when exiting the page, and closing a window unexpectedly terminates the program producing a crash dump instead of opening the login window. These faults degrade app stability on Windows platforms.
• issues/37096, issues/37280

• Build and Warning Anomalies: A false PRI263 warning occurs in .NET MAUI Blazor Hybrid projects due to the build tool misinterpreting wwwroot asset folder and file names as culture-specific resources, leading to misleading warnings without runtime exceptions. This causes confusion during development despite no actual asset issues.
• issues/37108

• Platform-Specific Test Flakiness: Certain LabelFeatureTests pass locally but fail consistently in the macOS continuous integration environment, indicating platform-specific test instability that requires investigation in an upcoming refactoring update. This flakiness complicates reliable automated testing on macOS.
• issues/37117

• Shell Background and UI Rendering Issues: Setting a gradient color on Shell.Background does not render correctly on iOS and Android, resulting in a white or gray background, and Shell.Background and Shell.BackgroundColor behave inconsistently across platforms, affecting navigation and tab bar backgrounds differently on Windows versus Android and iOS. These inconsistencies impact UI appearance and user experience.
• issues/37138, issues/37149

• Accessibility and VoiceOver Problems: VoiceOver on Mac does not announce roles or interactivity of task items and fails to read project descriptions in the .NET MAUI SDKs sample app, causing accessibility barriers. Additionally, the selected navigation menu item state is indicated only by color, which is problematic for low vision users, suggesting the need for non-color visual indicators.
• issues/37140, issues/37142, issues/37144

• Android UI Property Reset Issues: Resetting BorderColor, BorderWidth, or CornerRadius on a RadioButton to default values does not clear the previously rendered border, causing it to remain visible. This issue leads to inconsistent UI appearance after property resets on Android.
• issues/37145

• Semantic Properties and Accessibility on Android: Setting SemanticProperties.Description on an Entry control does not update the Android native view's contentDescription, causing accessibility tools to miss semantic descriptions, unlike the behavior with Label controls. This limits accessibility support for Entry controls on Android.
• issues/37151

• Background Property Reset Issues on Mobile: Setting the Background property of a Label to null at runtime does not reset it to transparent, causing the previously set custom color to persist on iOS and Android. This behavior prevents expected background clearing in UI updates.
• issues/37180

• Shell Flyout Footer and Map Element Tracking Bugs on iOS and Mac Catalyst: Replacing Shell.FlyoutFooter at runtime on iOS does not fully detach the previous footer, causing layout and memory issues, and MauiMKMapView.AddElements replaces rather than appends tracked map elements, dropping others and leaving stale references. These bugs cause unexpected layout updates and stale data retention.
• issues/37187, issues/37229

• CollectionView Scroll Regression: In version 10.0.90, ScrollTo(0) no longer works on CollectionView when IsGrouped is true, despite working in earlier versions, causing regression in grouped list navigation.
• issues/37259

• Android App Installation Failure on .NET 10: Users cannot install deployed Android apps on devices running version 14.2.0 after upgrading to .NET 10, although installation works on .NET 9, blocking deployment on newer Android versions.
• issues/37262

• iOS ScrollView SafeArea Layout Issues: Setting SafeArea to Default or Container in landscape mode causes left and right layout misalignment, and using SafeArea set to SoftInput causes top and bottom labels to fail edge-to-edge alignment within ScrollView on iOS. These layout problems affect UI correctness in different SafeArea configurations.
• issues/37263, issues/37264

• Android Custom EntryHandler Mapper Failure with Material3: Enabling Material3 disables the custom EntryHandler mapper calls in MAUI Android projects, causing loss of debug output on emulator and devices. This breaks custom handler functionality when Material3 is active.
• issues/37275

2.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 11

Summarized Issues:

• Rendering Issues with UI Elements: Several issues describe problems with UI rendering in .NET MAUI, including gradients not displaying correctly on multiple platforms and layout shifts causing visual glitches on Android. These rendering problems affect user experience by either showing solid colors instead of gradients or causing temporary gaps and jankiness during interactions.
• issues/10445, issues/37075, issues/37279

• App Size and Build Optimization: There are concerns about app size increases due to image processing changes and proposals to add configurable properties for ReadyToRun publishing to balance app size and runtime performance. These issues highlight the trade-offs between build output size and app efficiency, impacting deployment and user experience.
• issues/25750, issues/36587

• New Feature Development and Framework Enhancements: Proposals and implementations include adding a new CardButton control with animation and unifying the FlyoutViewHandler for iOS in .NET 10 to replace legacy renderers. These enhancements aim to improve UI capabilities and simplify code maintenance across device scenarios.
• issues/33083, issues/36667

• Debugging and Tooling Problems: Debugging issues are reported where breakpoints and debug output do not work on iOS devices and simulators despite various troubleshooting steps. This hampers developers' ability to diagnose and fix problems efficiently in .NET MAUI apps.
• issues/37126

• Source Generation and Binding Errors: A problem with CommunityToolkit MVVM's [RelayCommand] attribute causes source-generated properties to have incorrect types, leading to binding errors in XAML when source generation is enabled. This issue affects data binding reliability and developer productivity.
• issues/37231

• Release Management and Workflow Improvements: Issues cover release readiness tracking for .NET 10 SR9 and improvements to GitHub Actions workflows to enhance consistency, security, and resource usage during CI processes. These efforts support smoother release cycles and more efficient automation.
• issues/35431, issues/35867

2.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.

III. Pull Requests

3.1 Open Pull Requests

This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Opened This Week: 20

Key Open Pull Requests

1. [iOS] ScrollView: Clamp ScrollTo requests against AdjustedContentInset: This pull request improves the iOS ScrollView implementation by clamping programmatic ScrollTo requests against the UIScrollView’s AdjustedContentInset, establishing a consistent content-coordinate convention for scroll offsets that aligns iOS with Android and CollectionView behavior, fixing issues where scrolling to the end or to zero did not account for safe area insets, and enhancing deferred scroll requests, viewport calculations, and internal offset reporting to ensure accurate, inset-aware scrolling without raising spurious scroll events.

• URL: pull/37060

• Associated Commits: e856c, 347ee, 0ddb7, 7f427, 94799, 6894b, ab129, b6183, 2a264, b89b6, e3f38

2. [Testing] Refactoring Feature Matrix UITest Cases for Entry Control: This pull request refactors the Entry control UI test cases by adding new bindable properties, improving event handler logic, enhancing the ViewModel with helpers and a reset method, and updating UI elements to boost test coverage, accessibility, and code maintainability.

• URL: pull/37111

• Associated Commits: 315b7, 5a9ff, eaab2, 7efa6, d0f7c, 6322e, 07f17

3. [Windows] Map: Fix crash when leaving a page: This pull request fixes a crash in the Windows MapHandler by preventing mutation of native MapControl layers during temporary unloads, preserving the internal WebView2 state across visual-tree removals, and moving permanent cleanup to the DisconnectHandler to ensure stable reloads and proper resource management.

• URL: pull/37154

• Associated Commits: 67174, ef671, 121ca, 21375, 72d7b, 34990, 1e3b5

Other Open Pull Requests

• Android Picker horizontal drag scrolling fix: This pull request restores horizontal drag scrolling for long selected text in the Android Picker control by delegating touch events to Android’s native ScrollingMovementMethod without enabling the movement method itself. This fixes the issue caused by disabling the default movement method that previously prevented horizontal scrolling of selected text.
  • pull/37232

• TimePicker UI test enhancements: This pull request refactors and significantly enhances the TimePicker feature matrix UI test cases by adding programmatic control actions, event tracking, nullable time support, and improved ViewModel properties. It also expands UI test coverage, accessibility improvements, and consistent UI and ViewModel updates to make the control more robust and testable.
  • pull/37252

• ResourceDictionary lazy loading fix: This pull request fixes the issue in .NET 11 MAUI where lazy ResourceDictionary factories were being eagerly resolved during resource propagation by changing resource iteration to use keys only. This preserves laziness, improves performance and memory usage, and ensures correct handling of explicit-null resource updates across multiple platforms.
  • pull/37257

• Bottom tab bar gradient background rendering: This pull request fixes the issue where gradient backgrounds were not rendering on the bottom tab bar in .NET MAUI Shell by updating background selection logic and platform-specific implementations on iOS and Android. It enables consistent native gradient rendering while preserving existing solid-color behavior and compatibility.
  • pull/37137

• Android SwipeView accessibility improvements: This pull request improves accessibility on Android by ensuring swipe item commands in SwipeView are properly executed when activated via screen readers like TalkBack. It adds a new accessibility delegate to handle ACTION_CLICK events and includes tests to verify this functionality.
  • pull/37143

• Material 3 theme colors restoration for Android Shell: This pull request restores the use of native Material 3 theme colors for Android Shell and TabbedPage appearances by capturing and reapplying the platform's default colors when custom colors are cleared. It replaces the previous fallback to hardcoded defaults that caused incorrect theming under Material 3.
  • pull/37147

• Label background clearing on Android and iOS: This pull request addresses the issue where setting a Label’s background to null did not clear the previous background on Android and iOS. It modifies native handlers to properly remove existing backgrounds, including solid colors and gradient layers, ensuring transparency is correctly applied.
  • pull/37182

• MauiXaml build process platform-specific XAML exclusion: This pull request fixes the MauiXaml build process issue where source code was generated for every XAML file regardless of platform-specific conditions. It extends removal logic in build targets to exclude non-active platform XAML files from compilation, preventing duplicate InitializeComponent declarations across multiple platforms.
  • pull/37176

• Image scaling fix in HorizontalStackLayout on iOS and Mac: This pull request fixes an issue where images inside a HorizontalStackLayout did not enlarge to respect explicit HeightRequest or WidthRequest values on iOS and Mac. It modifies image scaling logic to allow images to scale up beyond their native size when explicit size constraints are set.
  • pull/37267

• Memory leak test fixes on Windows and macOS: This pull request fixes memory leak test failures on Windows and macOS by properly awaiting asynchronous view attachment operations in device tests. This ensures accurate garbage collection assertions and re-enables previously failing test cases.
  • pull/37278

• View margin layout fix for large margins: This pull request fixes the issue where views with margins larger than their parent bounds were irregularly or visually reversed in placement. It clamps the available alignment space to a minimum of zero in horizontal and vertical alignment calculations, preventing negative offsets and ensuring correct layout positioning.
  • pull/37080

• MacCatalyst UI test performance instrumentation: This pull request adds instrumentation to profile and collect detailed performance data for slow MacCatalyst UI test shards. It logs NUnit test boundaries, Appium commands, element searches, waits, and screenshot timings without altering test behavior to analyze time spent on various UI test operations and identify bottlenecks.
  • pull/37120

• CI scanner evidence recurrence stabilization: This pull request fixes the CI scanner evidence recurrence issue by stabilizing canonical issue identity across runs and independently validating each run against its frozen evidence. It enforces strict historical error message evidence requirements for issue creation and reuse, improving pattern verification to prevent publication failures caused by conflated evidence keys.
  • pull/37194

• Trusted input handling for /review tests: This pull request fixes handling of trusted inputs by sealing the review skill, canonical CI facts, and gathered context before checking out untrusted pull request content. It ensures the agent accesses only root-owned, read-only copies under a designated trusted directory, eliminating implicit trust transitions and improving security and reliability in the review process.
  • pull/37219

• Polyline Geopath update fix on iOS and Mac Catalyst: This pull request addresses an issue where updating the Geopath of one Polyline caused other Polylines to lose tracking and retain stale MapElementId values. It modifies MauiMKMapView's element tracking logic to prevent overwriting the tracked elements list and ensures proper removal and clearing of MapElementIds.
  • pull/37265

• .NET 11 AOT profile updates for Mono: This pull request updates the .NET 11 AOT profiles in the Mono project to facilitate easier performance comparisons with CoreCLR. These updates are intended for benchmarking purposes and not for production use.
  • pull/37273

• Android Entry accessibility description update: This pull request updates the Android implementation to apply SemanticProperties.Description to the accessibility node’s contentDescription for Entry controls. This ensures semantic descriptions are properly exposed to accessibility tools like Appium and UIAutomator while preserving existing TalkBack behavior.
  • pull/37276

3.2 Closed Pull Requests

This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Closed This Week: 95

Key Closed Pull Requests

1. [inflight/current] Update SR10 visual test baselines: This pull request updates the visual test baselines for the SR10 candidate UI validation by adding the Android API 36 notch-device baseline for LayoutShouldBeCorrectOnFirstNavigation, and updating Mac baselines related to Label line height, character wrapping, and grouped CollectionView layout and selection visual state, with snapshots captured from the maui-pr-uitests build 1544766.

• URL: pull/37196

• Associated Commits: 9af1a, a6de9, 16671, 8266d, 12e80, afa93, c0558, 5b5ea, aa067, 767d5, aa598, f27ca, adbcf, e1080, ed4dc, 83264, e4bb2, 9d5fa, 2ee27, 85ef4, 3caab, 7b7dc, 8d030, 35872, b26ff, 3f7a0, d584d, b0a28, 188dc, 23a4e, ce793, 90a31, 184bb, f8beb, d9d9a, 8c3f3, abce5, 84c3e, 24029, 5e45a, af53f, ab3a7, 345bc, 86ed9, 185da, bccf4, bd680, 880b5, 8ea19, b3d16, f94d1, ca409, bac1a, bc3fc, c6346, 83d41, da477, 0852d, 320e8, e4761, c1ba9, 9186b, 10f9a, 497f5, 7453e, 23c68, ca3bf, 27887, 041cb, a786e, 3046a, 4786d, 474c0, 3c4da, e54ad, 98e21, f8c20, d670e, 7967c, 2c098, afa15, 07b0f, a3fac, 1085d, 8d9c3, 16ec1, b2fbc, 3295b, 32844, dc008, dc731, 65da5, fa4e4, 42978, 9584c, f28a8, 927ab, 1ee1b, a1888, dc77c, be7c6, 3f064, f7398, 62041, b9b23, 4ae06, 7bc32, a678c, 57815, 703d7, 67696, e1a7e, 9e11b, 0e414, 206ef, 92202, 36b7f, 620c2, d22a4, d9f0e, 5c5a9, 66659, dc9a4, 56454, 4adef, eb5ad, e535a, f90a1, ffcc2, fb6e2, bac71, 4ceb7, bfb1f, 957d9, 9251e, 3690b, 92b0d, 53204, b2b50, 60c2c, 95404, 8d213, 4d130, f3e78, ad088, 49d5d, d7893, 9beaf, 635c9, a2711, ea0c1, 451e5, f7963, c5203, 8cf93, 98676, 49917, d4806, 5bf13, cecb3, 87e4c, 12242, 03c5c, aa8df, 90080, 524d2, 0b68f, a4dcc, d5f69, fe116, e823b, 01c78, ef8d9, 9615c, 9fbd6, fe4b4, 38831, 0380f, 90e21, e814d, 52b8a, d1d89, 7fb15, 611ef, 0afcf, a6636, bc970, 4a4a1, 50dd9, f7563, bc071, 075e9, 44ada, 200d4, 81368, 9bc9b, f17d5, 21e43, 358d7, 95f30, d1f99, 7c637, 51726, 87a3a, 0cad7, ccb5f, 4f7cd, e3631, 05617, 2a489, 419f7, 5d428, 840d5, 4607e, d7ba6, fb5d4, 7dda7, cfe29, 9f746, 8da57, 23d6d

2. [automated] Restore Preview 7 merge history in net11.0: This pull request restores the original merge history of the .NET 11 Preview 7 branch in the net11.0 branch by reverting a prior squash merge and then merging the original Preview 7 commits with a normal merge commit, thereby preserving the full commit ancestry without changing any files.

• URL: pull/37155

• Associated Commits: c90f6, 4557d, 67c53, 3c347, d1ec4, f3e76, 5d0d1, 6602b, 59914, 0fb2e, e742d, f799b, d78e3, 7d30b, cce6d, c1a6b, f37fd, 3ade0, ec1ed, 50731, f12f0, 4b621, df35d, 75a60, 87197, 0ec3d, eb659, ec6fd, 20c66, 4cc57, 2c2f6, 9dcf1, b5535, c119c, 18698, fc682, df15a, b1eb9, 77f33, 2eb88, 2013a, 6fa52, 1150c, eb0cb, ade8e, 8a58e, dee83, 07be4, 137eb, c35d1, 6f89b, 205aa, 3cc82, a87ea

3. [Android] Make system chrome follow MAUI bar colors (opt-in): This pull request introduces an explicitly opt-in Android feature that synchronizes the status and navigation bar background colors with the effective MAUI NavigationPage, Shell, TabbedPage, and modal chrome colors, preserving existing theme behavior by default while enhancing visual consistency through centralized system chrome updates, gradient support, and careful handling of modal dialogs and icon appearances without adding public APIs.

• URL: pull/35463

• Associated Commits: c9a4f, 487b0, 9ee20, e075a, 5f036, 1e233, 0a18b, 27646, 2568b, ec4f1, 0c335, 2f28d, 0e509, 19002, d6904, c7cf6, 92547, 63de7, e39c4, 78017, 67634, fd748, 83890, fd4da, 94f61, 20f9b, e1521, ca647, 1f855, b2c72, 50261, 4793a, 1fc67, 635e6, 49440, b600f, 8c419, 11aa9, 9351a, 07066, e3c0c, 44772, 2c3f7, 2ee84, 1ef63, 731d0, d9030, 7e810, efb53, 607ca, 09a53, ed2c1

Other Closed Pull Requests

• Test and Test-Infrastructure Stabilizations: Multiple pull requests focus on stabilizing the .NET MAUI Preview 7 test suite by fixing UI test flakiness, improving screenshot retry tolerances, enhancing device-specific test coverage, and synchronizing test operations without modifying runtime or product code. These changes collectively improve test reliability and maintain the integrity of the Preview 7 release branch.
  • pull/37081, pull/36935, pull/37062, pull/37035, pull/36939

• Image Processing and Resizing Enhancements: Pull requests introduce a configurable ResizeQuality option to the Resizetizer tool, replacing deprecated APIs with modern SkiaSharp sampling options, and implement a deadlock-safe image scaling mechanism on iOS using CGBitmapContext. These improvements provide better image resampling quality control and resolve build errors related to deprecated UIKit graphics APIs.
  • pull/34559, pull/37057

• UI Template and Control Improvements: Several pull requests add an opt-in C# UI mode for the single-project app template, refactor the Switch control with enhanced test coverage and property support, fix the Switch control's ThumbColor reset behavior, and address Android Entry control text truncation issues. These changes improve UI flexibility, test robustness, and control behavior consistency across platforms.
  • pull/34863, pull/36939, pull/36750, pull/36750

• Shell and Navigation Bar Enhancements: Fixes include adding support for brush backgrounds on the Shell navigation bar, resolving large title collapse issues on iOS 26 for non-Shell NavigationPage scenarios, and synchronizing native and navigation titles while preserving safe-area settings. These updates ensure consistent visual behavior and correct layout handling across platforms.
  • pull/35491, pull/36511

• Splash Screen Theming Support: A pull request adds support for themed splash screens by introducing light and dark splash screen metadata to the MauiSplashScreen element, enabling Android and Apple platforms to generate appropriate night-qualified and asset catalog launch screens while maintaining backward compatibility.
  • pull/35710

• Android Permission and Input Handling Fixes: Fixes address stale permission requests causing duplicate key exceptions by enforcing main-thread validation, and resolve text truncation in the Android Entry control by managing native length filter application order. These changes improve stability and correctness in Android input and permission workflows.
  • pull/37056, pull/37052

• BlazorWebView and Android Startup Improvements: Pull requests introduce an opt-in StaticContentCacheControlProvider callback to customize cache-control headers for static assets in BlazorWebView, and simplify the Android Blazor startup process by consolidating JavaScript callbacks and improving message handling. These enhancements reduce flickering and improve startup reliability.
  • pull/35706, pull/35053

• FlyoutPage Renderer Refactor: The monolithic PhoneFlyoutPageRenderer on iOS and MacCatalyst is replaced with a layered FlyoutViewHandler architecture that improves maintainability, memory safety, multi-instance support, and aligns with the handler pattern used by other pages. This refactor fully implements gesture handling, layout, accessibility, and status bar/home indicator delegation.
  • pull/36676

• Android Window Insets and Keyboard Animation Fixes: Improvements to the Android MauiWindowInsetListener allow views attached during IME animations to receive safe-area inset padding immediately and ensure proper reapplication of insets at animation end, fixing layout issues where views initially render without padding and then jump after keyboard animation.
  • pull/37049

• Sample Template and Seed Initialization Fixes: Fixes ensure SQLite schema cleanup and table drops are awaited and serialized to prevent concurrency issues, improve deterministic parsing and validation of JSON seed payloads, and propagate errors properly to avoid false success states during sample data seeding.
  • pull/37122

• CI and Workflow Upgrades: Updates include upgrading GitHub Agentic Workflows compiler and related workflow lock files to stable versions, refreshing GitHub Copilot model assignments, enforcing GPT-5.6 Sol usage for PR review orchestration, and refining evaluation policies to maintain review diversity and production alignment.
  • pull/36772, pull/36707

• Manifest and Security Validation Fixes: A pull request fixes production CI scanner failures by improving manifest handoff, canonicalizing ASCII fingerprint casing, hardening threat detection against hidden Unicode characters and duplicates, restoring disabled tests, and allowing trusted emoji presentations to ensure robust manifest processing and validation.
  • pull/36958

• Windows Label Feature Matrix and Logging Improvements: Fixes revert a baseline image update to resolve test failures in the Windows Label Feature Matrix and reduce noisy logging related to missing font fallbacks on Windows and Android by treating unregistered font family fallbacks as expected behavior.
  • pull/37035, pull/35963

3.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.

If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.