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/ENHANCEMENT ☀️] [GOOD FIRST ISSUE] [PROPOSAL/OPEN] [AREA-XAML] Add OnBindingContextChanging: This issue requests the addition of an OnBindingContextChanging method to allow developers to execute code before the BindingContext of a ContentPage or ContentView changes, addressing a limitation where currently only post-change reactions are possible. The user provides a detailed use case involving a CollectionView with dynamic BindingContext changes and a custom control that needs to respond before the context updates to properly manage its drawing state.

   • The comments show multiple users expressing interest in working on the issue, with maintainers explaining timing constraints related to .NET version support and planning. A detailed technical discussion clarifies why the current OnBindingContextChanged override cannot intercept changes early enough, leading to a proposal for a new OnBindingContextChanging hook to be added before ApplyBindings runs, with an offer to draft a PR for this enhancement.
   • Number of comments this week: 5

2. [T/BUG] [PLATFORM/ANDROID] [PLATFORM/IOS] [AREA-CONTROLS-COLLECTIONVIEW] [S/VERIFIED] [S/TRIAGED] CollectionView (grouped): EmptyView handling is wrong when groups become empty: This issue addresses inconsistent behavior of the EmptyView in a grouped CollectionView when groups become empty or are removed dynamically, specifically on iOS and Android platforms. On iOS, the EmptyView incorrectly appears over the list when groups exist but have no items, while on Android, the EmptyView fails to display after the last group is removed at runtime, despite the collection being empty.

   • The comments confirm the issue was reproduced and validated on both platforms, followed by a detailed fix addressing platform-specific root causes; the fix was tested thoroughly with the reporter’s project, confirmed to work perfectly, and is planned for release in .NET 10 SR12 after some release timing clarifications.
   • Number of comments this week: 2

3. [T/BUG] iOS: When using cellular data, ConnectivityChanged toggles repeatedly between Wifi and Cellular: This issue describes a problem on iOS devices where the ConnectivityChanged event repeatedly toggles between WiFi and cellular data profiles even when WiFi is turned off and the device is using cellular data. The user reports that this behavior does not occur on Android and that the event should only fire when there is an actual change in connectivity, but instead it fires continuously without real changes.

   • The comments suggest that the issue may be related to specific edge cases such as an expired VPN connection causing instability in the connectivity profile, and another case where the SIM is not installed but WiFi is enabled, both leading to repeated toggling between WiFi and cellular states.
   • Number of comments this week: 2

4. [T/BUG] [PLATFORM/WINDOWS] [PLATFORM/ANDROID] [AREA-DRAWING] [S/VERIFIED] [S/TRIAGED] PathGeometry results in HRESULT E_FAIL - Invalid number: This issue describes a problem where rendering a specific PathGeometry in a .NET MAUI app causes a fatal error on Windows with an HRESULT E_FAIL due to an invalid number, while on Android the PathGeometry simply does not render. The root cause was identified as a bug in the GeometryHelper.FlattenArc method, which can produce NaN points when the computed segment count truncates to zero, leading to a crash on Windows and silent failure on Android.

   • The comments include a repro project and confirm the issue occurs on Windows and Android with different failure modes. The problem was traced to a calculation error in the arc flattening logic causing invalid geometry points. A proposed fix involves ensuring the segment count is at least one to avoid division by zero and NaN values.
   • Number of comments this week: 1

5. [T/BUG] [PLATFORM/WINDOWS] [AREA-DRAWING] [S/VERIFIED] [S/TRIAGED] Certain kinds of PathGeometry result in an unhandled runtime exception : This issue describes a problem where certain PathGeometry objects created from SVG path data fail to render correctly, causing an unhandled runtime exception on Windows and no display on Android. The user reports that while some SVG paths convert and render successfully, others trigger errors related to invalid numbers during rendering, and a workaround involving SVG optimization tools has been found but is not ideal.

   • The comments confirm the issue is reproducible on Windows and Android, link it to a known bug involving segment count truncation in geometry flattening functions, and suggest a potential fix by ensuring a minimum segment count to avoid invalid calculations; the issue has been added to the backlog for future resolution.
   • Number of comments this week: 1

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: 20

Summarized Issues:

• Rendering and UI glitches on Android and Windows: Several issues describe rendering problems including a division by zero bug in GeometryHelper causing crashes on Windows and silent failures on Android, keyboard flickering on Android API 36, and a WebView inside a ScrollView blocking scrolling on Mac and Windows. These issues disrupt user experience by causing crashes, flickers, or blocked interactions across platforms.
• [issues/38751, issues/38799, issues/38838]

• TabbedPage and Tab icon color inconsistencies on Android: After rebuilding the Children collection of a TabbedPage while visible, the selected tab's icon loses its custom SelectedTabColor and falls back to a native color, while unselected tabs and text remain correct. This causes inconsistent visual feedback for users interacting with tabs.
• [issues/38765]

• Gesture recognizer API limitations: There is a request to expose public interfaces or dispatch mechanisms for tap and pointer gesture recognizers in Microsoft.Maui.Controls to enable custom renderers to fully implement these gestures with complete event semantics and platform fidelity, similar to existing pan, pinch, and swipe gestures. This limitation restricts developers from achieving consistent gesture handling across platforms.
• [issues/38783]

• Focus and keyboard issues on Android Entry controls: Modifying the FontAttributes property of an Entry control prevents the keyboard from appearing immediately on focus, requiring a second tap to show the keyboard. This degrades user input responsiveness on Android devices.
• [issues/38819]

• CarouselView CurrentItem update inconsistency on Android: Removing the current item with looping disabled causes the CurrentItem property to update incorrectly on Android, differing from iOS behavior and leading to inconsistent user experiences across platforms.
• [issues/38821]

• Shell flyout and visual state regressions causing hangs and high CPU usage: Setting the Background property in a Shell.ItemTemplate VisualState triggers a re-entrant loop on Android and iOS, causing the Shell flyout to hang with 100% CPU usage and ANRs. This regression severely impacts app responsiveness and stability on both platforms.
• [issues/38813]

• Editor scrolling issues on iOS simulator: The editor becomes unscrollable after rotating the iOS simulator on iPhone Pro Max models, affecting UI tests related to character spacing customization. This limits testing and user interaction in simulator environments.
• [issues/38802]

• ShareTextRequest API enhancement proposal: A feature request suggests adding a preview image property to ShareTextRequest to enable rich image previews when sharing text or URIs on supported platforms, improving the share sheet's visual presentation without custom platform code.
• [issues/38824]

• Non-deterministic XAML generator output: The MAUI XAML generator produces non-deterministic ordering of attributes in Global.Xmlns.cs depending on metadata reference order, causing unnecessary code changes and issues with Edit and Continue or Hot Reload workflows.
• [issues/38841]

• ListView image loading exceptions on iOS: An InvalidOperationException occurs when a MAUI ListView with HasUnevenRows set to true loads URI images on iOS, due to a null PlatformView during initial row-height estimation, resulting in logged exceptions without crashing the app.
• [issues/38845]

• ConnectivityChanged event toggling on iOS: The ConnectivityChanged event repeatedly toggles between WiFi and cellular profiles every 5-10 seconds on iOS devices using cellular data with WiFi off, causing unnecessary event firing despite no real network changes.
• [issues/38851]

• XAML parsing regression with x:Array on iOS and macOS: A recent pull request introduced a regression causing device test failures on iOS and macOS when using the parsed XAML feature x:Array, impacting cross-platform XAML compatibility.
• [issues/38882]

• Android emulator deployment failure due to storage issues: Deploying a .NET 11 RC1 SDK-built app to an Android emulator fails with an unclear error caused by insufficient internal storage, requiring manual uninstallation of the existing app to resolve.
• [issues/38895]

• Text scaling issues in Shell flyout on iOS: Text inside the Shell flyout does not dynamically rescale when the system text size changes at runtime, requiring an app relaunch to update font sizes, which negatively affects accessibility and user experience.
• [issues/38909]

• Severe CollectionView performance regressions on Android: Starting from .NET MAUI 10.0.100, CollectionView with GridItemsLayout suffers from extremely slow ItemsSource assignment and scrolling due to inefficient, uncached span group index calculations causing super-linear time complexity and UI thread blocking, leading to ANRs during flings with large data sets.
• [issues/38925, issues/38926]

• Modal navigation crash on Windows: Clicking the "Push Modal Page" button in a test case causes the app to crash with an exception on Windows instead of navigating, indicating a regression in modal navigation behavior.
• [issues/38949]

• CollectionView ItemSpacing discrepancy on Windows: The ItemSpacing property in CollectionView's LinearItemsLayout appears almost three times larger on Windows compared to Android and possibly Mac/iOS, causing inconsistent visual layouts across platforms.
• [issues/38959]

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: 25

Summarized Issues:

• UI Layout and Rendering Issues: Several issues describe problems with UI layout and rendering across platforms, including improper content centering in Buttons with images and text, TabBar overlapping ContentPage on iOS, extra space in Labels with word wrap on Android, and ScrollView not scrolling on MacCatalyst. These problems cause visual glitches, incorrect sizing, or unresponsive UI elements that degrade user experience.
• issues/10005, issues/10591, issues/22853, issues/36042

• Navigation and Interaction Failures: Navigation deadlocks and gesture regressions affect app usability, including a deadlock in iOS FlyoutPage navigation caused by rapid back button presses, a regression in swipe-to-reveal gestures on Android SwipeView, and layout update delays after device rotation requiring user interaction to render. These issues block or delay expected navigation and interaction flows.
• issues/10539, issues/36570, issues/37414

• Platform-Specific Crashes and Exceptions: Multiple crashes and exceptions occur on iOS and Android, such as a SIGABRT from GestureManager due to null PlatformView, a native SIGSEGV crash in Mono runtime on Android during Shell navigation, an ArgumentOutOfRangeException in iOS CarouselViewHandler2 during teardown, and a build failure in iOS native linking with unresolved Xamarin symbols. These critical failures cause app crashes or build breaks.
• issues/35628, issues/37376, issues/36754, issues/35658

• Regression Bugs in .NET MAUI 10.0.100 and Later: Several regressions introduced in version 10.0.100 affect control behavior and platform compatibility, including editor controls not becoming editable on iOS, MediaPicker throwing exceptions when selecting multiple photos, numeric Entry controls ignoring locale decimal separators on Android, and CollectionView crashes when removing grouped items. These regressions break previously working functionality.
• issues/37815, issues/37878, issues/38213, issues/38321

• Visual and Animation Artifacts: Issues with animations and visual elements include persistent single-pixel artifacts on iOS when animating Shapes.Path with combined Scale and Opacity, and inconsistent Shell background color behavior across platforms where Windows does not apply background color to the tab bar. These visual inconsistencies affect UI polish and user perception.
• issues/36761, issues/37149

• Accessibility and Screen Reader Problems: Accessibility is impacted by VoiceOver on macOS not announcing combo box roles and states correctly, causing challenges for screen reader users in the Developer Balance app. This limits usability for users relying on assistive technologies.
• issues/36471

• File System and API Limitations: There is a need to expand .NET MAUI APIs to allow reading and writing files in public folders on Android, as current file system helpers restrict access to application-private folders, limiting file visibility and transferability. This limitation hinders common file management scenarios.
• issues/13939

• Build and Tooling Warnings: A false PRI263 warning occurs in .NET MAUI Blazor Hybrid projects due to MakePri.exe misinterpreting static web assets as language-qualified resources, generating misleading warnings without actual resource loading errors. This causes confusion during build processes.
• issues/37108

• Window and Titlebar Customization Requests: There is a feature request to customize the window titlebar and MenuBarItems fonts and styles on Windows, including changing the titlebar color to dark red and setting fonts to 'Helvetica' to match company themes. This reflects a demand for enhanced UI theming capabilities.
• issues/9837

• Layout and Rendering Issues on Windows: A problem exists where a MAUI WinUI app using ControlTemplates with ContentPresenter controls fails to render any content on Windows, despite working on other platforms and previous versions, indicating a platform-specific rendering regression.
• issues/37798

• Keyboard and Modal Page Layout Regression: On iOS, dismissing a modal page with the soft keyboard visible causes the underlying page to remain shrunken due to a missing layout pass after keyboard state cleanup, resulting in improper scrolling behavior. This regression affects user interaction with modal dialogs.
• issues/37691

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: 26

Key Open Pull Requests

1. September 22nd, Candidate — .NET 10 SR12 (10.0.120): This pull request is a draft candidate snapshot for the .NET MAUI 10 SR12 (10.0.120) release, created from the frozen inflight/current snapshot, intended to track and replace a previous PR with the correct source branch, containing 103 commits ahead of main, and serving as a basis for review and validation before cutting the SR12 release branch without changing inflight/current or release refs.

• URL: pull/38782

• Associated Commits: 063d2, c60cb, b4224, dc928, d9958, f5a03, 7de59, 42a83, 209f8, 7d132, d2618, d83ed, 36b63, cb233, c43a5, 6fc0e, f22a8, e4193, 3bf27, dcc10, bdb2b, d7872, ea53a, 24d0b, 13009, b2470, 2b4d2, 95105, ccc91, 22ed7, c7b53, 5b22d, 7d700, f0bd4, b4f00, 736ea, 872ef, 6a910, ddced, 4957e, e7cf1, da5e5, 0ed6d, 79f98, d35ca, d22e5, bb6b6, 585fb, f9497, 143f3, 49f03, a421e, 95b7c, f4082, 13ad0, e9335, 92587, aa9ff, 37705, 1d56b, 3bf28, 077c1, 0b299, c5d15, 91541, d313f, 304d3, 1e5a0, 0d108, b6e00, 2b229, 0debc, 92ff2, 62dcb, 19d13, d4b28, 2ba60, a0636, ecc90, e84d4, cf07e, 9d10e, 90589, ed51b, ff740, 7b650, d0ade, 28ec1, 9593d, 630b0, 67a62, d37eb, ecf53, aedfb, d7df0, 9b5c8, 0ba32, 93ee7, b3cef, ef1f0, d52a0, 4daad, 1fcb1, 1d1ef, 9e5f7

2. Deflake UI regression tests instead of quarantining them: This pull request aims to deflake UI regression tests by replacing flaky screenshot-based checks with more reliable native assertions, isolating and stabilizing test fixture state across platforms, fixing lifecycle and input event handling issues, and improving test infrastructure without quarantining tests or broadening exclusions, thereby enhancing test reliability and coverage across Android, iOS, MacCatalyst, and Windows environments.

• URL: pull/38822

• Associated Commits: c1f8a, dad48, 9f91b, 6b75c, c5389, 9ad08, 2af96, 2f6a9, b1607, b27ed, 960c5, b52ed, 6dfee, 78edb, d2981, 553fd, 51cc2, f4d9a, ccf50, 499a3, f1044, 64f3d, 029fc, 68a61, 122e5, b594a, 0d7dd, cb24d, c01bd, 6228f, 7c84f, dac93, f0235, df978, 87708, 8d998, 575cb, e7db3, 85e5d, a25b5, 114e0, 64b2c, 0693f

3. Move managed device and UI coverage to unit tests: This pull request moves and deduplicates a large number of managed device and UI test methods into existing host-based unit test suites, removes over 230 unused snapshot baselines across multiple platforms to reduce test redundancy and improve reliability, while retaining native coverage for behaviors that cannot be validated by managed tests, and includes follow-up fixes to enhance CI stability and test fixture reliability without changing production code.

• URL: pull/38780

• Associated Commits: 33143, 7df8d, be085, e2dc4, ee090, 36984, 52f8f, 01ac1, 0434a, 5284b

Other Open Pull Requests

• Memory Leak Fixes in Shell and PathGeometry: This topic covers pull requests that address memory leaks by improving event subscription management and lifecycle handling. One PR fixes a managed memory leak in ShellItem.MenuItem by properly managing event subscriptions and parent references in the internal MenuShellItem wrapper, while another replaces strong event subscriptions with weak event proxies between PathGeometry and shared PathFigureCollection to ensure proper garbage collection.
  • pull/38804, pull/38946

• iOS Shell Navigation and Layout Fixes: These pull requests fix navigation inconsistencies and layout issues in the iOS Shell renderer and handler. They ensure consistent use of the active More navigation controller to prevent exceptions and blank pages, and correct the detail pane positioning when using FlowDirection.RightToLeft with FlyoutBehavior.Locked.
  • pull/38805, pull/38888

• UI Test Stability and Quarantine Improvements: This group of pull requests improves UI test reliability by updating baseline images, porting quarantine strategies to net11.0, and adding quarantines for flaky tests based on evidence. They maintain method- and platform-scoped quarantines without broad disables, update inventories, and adapt tests for stricter analyzers to reduce costly reruns.
  • pull/38843, pull/38856, pull/38777, pull/38917

• iOS Layout and Toolbar Enhancements: These pull requests improve iOS layout accuracy and toolbar behavior by using scene-aware window display references and supporting UIKit's new toolbar behavior on iOS 27.1. They maintain legacy rendering on older iOS versions and Mac Catalyst while preserving Shell menu metadata after dynamic updates.
  • pull/38911, pull/38947

• Foldable Device Support in TwoPaneView: This pull request adds staged support for iPhone Duo foldable devices by implementing element-scoped TwoPaneView layouts that split around active iOS division reserved regions using native APIs. It maintains compatibility with existing Android behavior and older iOS versions without introducing new public APIs.
  • pull/38915

• Android CollectionView and TabbedPage Fixes: These pull requests optimize Android UI components by preventing unnecessary item view recreation in CollectionView header/footer updates and fixing a bug where the selected tab icon loses its color after tab children are rebuilt. They include test cases to verify these improvements.
  • pull/38808, pull/38801

• Essentials ShareTextRequest PreviewImage Addition: This pull request adds a PreviewImage property to the ShareTextRequest class, enabling share sheets on iOS, Mac Catalyst, and Android 10+ to display a preview image alongside shared text or links. It includes platform-specific implementations and updates to the sample app and tests.
  • pull/38825

• XAML Reflection and Build Tool Fixes: These pull requests fix issues related to XAML loading and build tooling by adding DynamicDependency annotations to preserve constructors removed by the linker and resolving a MissingMethodException in the Resizetizer tool by ensuring correct SkiaSharp DLL loading.
  • pull/38840, pull/38883

• Shell Flyout Visual State and FlyoutHeader Test Fixes: These pull requests fix UI responsiveness and test failures by adding guards against re-entrancy hangs in Shell flyout visual state transitions and updating the FlyoutHeader minimum-height UI test to align with lifecycle changes, avoiding premature view loading.
  • pull/38887, [pull/38879](https://github.com/pull/38879]

• Apple Icon Composer .icon Bundle Support: This pull request adds support for Apple Icon Composer .icon bundles in the MauiIcon item on iOS and Mac Catalyst, bypassing Resizetizer/SkiaSharp and passing contents to the Apple asset compiler. It maintains legacy behavior for other icon types and improves validation and incremental build tracking.
  • pull/38958

• Issue Repro Automation and Global XML Namespace Determinism: These pull requests add a maintainer-only issue-comment trigger for automated issue repros using GPT and make global XML namespace generation deterministic by sorting namespaces before emitting code, ensuring consistent output and adding regression tests.
  • pull/38807, pull/38842

• .NET SDK Version Updates: These pull requests update the Microsoft.NET.Sdk to version 11.0.100-rc.2.26475.136 and align the tools.dotnet SDK version in global.json to the final RTM release, ensuring consistency across project configuration files and resolving build failures caused by version mismatches.
  • pull/38950, pull/38951

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: 62

Key Closed Pull Requests

1. [WIP]Fix SwipeItemView Command Memory Leak: This pull request fixes a memory leak in SwipeItemView.Command by replacing its strong event subscription to the command's CanExecuteChanged event with a weak subscription using MAUI’s existing WeakCommandSubscription helper, ensuring that when the command outlives the SwipeItemView, the view and its visual subtree can be garbage collected properly without being retained by the command’s event.

• URL: pull/38316

• Associated Commits: 69732, 784c3, e2fab, 92142, b9fe7, b1396, 4bd3f, 59e40, 5fafe, 8dddc, e7a8a, e095c, 413a5, cc38d, 8002d, 5a547, 909ca, 27aab, 15e7c, 5e9e4, 705f9, 1c210, 7c748, 3dab3, c85b1, f2d5a, bc2ad, cacd9, e42cd, 23a5e, 4decd, 95bde, 94ac2, e4db4, 30e92, 67b60, d91d4, 40db7, 26bb1, c8863, 9551a, af3f4, 3bdd4, 61b0b, 85768, ac548, d0129, 1fb67, 3347b, c6c4d, 4087e, b1bbe, 1a807, 438de, 2ef02, ebd65, a4ad5, 16f1b, dfdb3, bf6e2, 7aac4, 71bfa, 13f48, 2d9b8, 5a116, bb995, 1db4c, 4d9e6, 75628, 5c86e, a0aa0, c43ea, 36d5f, cdedf, 442b5, 98ffa, fd20d, 45b8b, 2f912, f8475, 5a4b4, 5b7ec, 84a9c, baa74, b0451, d4817, f3c28, d0250, 5509d, e86a6, ec77b, 001d1, d006f, c20c8, dad19, ac0d1, e7650, a70fe, 70130, c603b, 25e4d, 91170, bc2a4, fa814, fbd6e, 57937, e7d0c, 53a37, 26233, 458e8, 1ba5d, 8750f, 9190b, 3b9c6, 8896f, 308e7, 6090c, 1bc7f, bc03c, 5274f, f3fec, 9bafa, 13b30, 6126c, 7d2b8, 10654, 02aa7, 0d248, 87541, 70637, 62c5f, 04dff, b42de, f2f0a, 92cd4, e2f01, d9bf1, 7fc52, a8e0f, b0e43, ceea2, 0f4b0, a8adf, 86547, 4f30d, 480a3, d11cd, 06a4d, c460b, 7c35f, 07b27, d6373, 73442, 577a2, 9e26f, 186e7, 046a7, 6822e, e1398, 58e06, 94f0f, b8594, c412e, 205ab, dba44, d22d3, 25ca0, fea79, fc426, 504c2, 7db9a, 5586a, 7d2fb, 68fca, b17a1, ae3f0, 2427b, fd8f7, 1f2d5, 9c8e1, 000f4, 01a03, 456df, 67440, 98b75

2. September 22nd, Candidate — .NET 10 SR12 (10.0.120): This pull request is a draft candidate snapshot for the .NET MAUI 10 SR12 (10.0.120) release, which freezes the source at a specific commit, tracks 103 commits ahead of the main branch, uses an isolated frozen feature branch without modifying release refs, retains existing version and CI labels without final stabilization changes, and awaits further review and validation before cutting the SR12 release branch.

• URL: pull/38779

• Associated Commits: f0824, c1f82, ba0a4, 42204, 9c995, 39e1c, 8ced4, 8a0dc, 863cd, 80446, 07a11, 3c503, e9b58, 7d086, f3456, c16a6, 08871, 94265, f68d2, ce8e4, 43458, 166ce, 9dc68, a332d, cc631, 810be, 32269, 437d8, ff8ef, 10762, 94175, 4c20e, 99f40, 03e65, d4a0a, 43510, cbfd6, b78fa, e3bdf, 35bcb, 05831, 600d9, 1514e, b0dd0, d5c3d, 55920, 90851, 9ffb7, 554e4, 867e0, e60ce, 451bf, c113a, 9bfed, 5b95c, 6c983, 385b8, 151a2, c51a4, c72ab, 43c87, 824ac, c0975, 1799e, 075ae, 5ee1c, 8628b, 992f3, 418d6, dea9d, 94eff, 277f4, 0d8ef, 1c7ae, 945e8, 2257b, 59484, a1ab8, af4df, a0e36, 3edff, c355d, ff966, ec418, da040, 92007, 6e299, be0d1, 51377, 95980, fd648, 85268, d05bc, 70982, 80d74, 913e8, 5833a, 0085c, 9bbf3, b8914, 04272, 15383, 1aa45

3. [WIP] Fix SwipeMenuItems were rendered to the full width of the SwipeView instead of their measured width on Android, iOS, and macOS: This pull request fixes the issue where SwipeMenuItems were incorrectly rendered to the full width of the SwipeView instead of their measured width on Android, iOS, and macOS by accurately measuring the native button sizes and converting them to device-independent pixels, thereby ensuring proper layout and appearance across these platforms.

• URL: pull/38271

• Associated Commits: 6ff8a, d9d3e, b08ec, c7f37, 89de7, cda5f, 4a495, c604b, 88394, a4e59, 54d85, 9fc7a, 7046f, d0762, a3996, ba07a

Other Closed Pull Requests

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.