Weekly GitHub Report for Maui: September 15, 2025 - September 22, 2025 (12:01:07)

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. [Performance] Reduce (SourceGen/XAML) Binding generated code: This issue addresses the performance overhead caused by the current generated code for Binding in .NET MAUI’s Source Generators and XAML, proposing to optimize it by only passing and setting the binding parameters explicitly specified by the developer. It suggests leveraging compile-time knowledge of default binding modes and eliminating unnecessary property setters to reduce CPU and memory usage, thereby improving AOT compilation success and runtime navigation speed on complex pages.

   • The discussion elaborates on the feasibility of accessing default binding modes at compile time, the potential need to handle built-in controls specially, and the importance of benchmarking to quantify improvements. Contributors agree on the value of minimizing allocations and redundant instructions, propose eliminating BindingExtension and moving certain logic outside generated code, and emphasize incremental, targeted optimizations to achieve meaningful performance gains.
   • Number of comments this week: 5

2. Close App or Wait on loop: This issue describes a problem where a popup repeatedly appears on Android Maui apps, indicating the app is not responding and asking whether to close or wait. The popup continues to reoccur in a loop every few seconds even after the app resumes from a breakpoint, forcing users to kill the app to stop the notifications.

   • Commenters confirm the popup never disappears without killing the app and note that while hitting a breakpoint normally causes the app to freeze and trigger such a popup, the repeated looping behavior is unusual and has been observed by others as well.
   • Number of comments this week: 3

3. Why the close button on the left side and in other computers on right side?: This issue concerns the inconsistent positioning of the close button in a MAUI app executable, where it appears on the left side on one Windows 10 computer and on the right side on another. The user is seeking to understand what factors influence this behavior and how to ensure the close button consistently appears on the right side across different machines.

   • The comments request additional details and screenshots to better understand the issue, and the user provides images showing the close button on different sides on two Windows 10 computers. The user also asks for an explanation of whether computer settings affect this behavior and how to configure the app to always display the close button on the right, but no solution or further response is provided.
   • Number of comments this week: 3

4. Navigation.SetTitleView does not work in ios 26: This issue reports that the Navigation.SetTitleView method no longer functions correctly on iOS 26, despite working in previous versions of .NET MAUI. The user provides a sample project and screenshots demonstrating the problem and notes that this behavior is a regression affecting the iOS platform specifically.

   • The discussion requests a minimal reproducible example and code snippet, which the user provides along with visual evidence of the issue on Android and iOS 26. A temporary workaround involving adding a key to the info.plist file is suggested to revert to the older iOS appearance, with a note that using the new iOS 26 UI requires implementing a NavigationRenderer.
   • Number of comments this week: 3

5. [IOS,MAC] ScrollView Content Misaligned in RightToLeft FlowDirection: This issue describes a problem where dynamically adding child views to a ScrollView during the Scrolled event causes layout misalignment and some elements to be rendered outside the visible bounds when the FlowDirection is set to RightToLeft on iOS and macOS platforms. The problem occurs in MAUI versions 9.0.30 and above but is not reproducible in versions below 9.0.30 or in .NET 10, with a workaround involving native platform arrangement and bypassing RTL logic.

   • The comments confirm the issue is reproducible on iOS and Catalyst platforms in MAUI versions 9.0.30 and later, but not in earlier versions or .NET 10. Visual evidence was provided showing the problem on Mac and iOS, supporting the original report.
   • 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.

1. Nullable Enums do not bind in XAML: This issue describes a problem where nullable enums fail to bind correctly within a custom control's bindable property in a XAML environment, with the setter method not being triggered during binding. The problem affects all versions on iOS and Android platforms, and the suggested workaround is to avoid using nullable enums by adding an explicit unset or none value to the enum instead.
2. App crash after invoked FilePicker.Default.PickAsync in administrator mode and release mode of the Unpackaged app: This issue describes an application crash that occurs specifically when invoking the FilePicker.Default.PickAsync method in an unpackaged app running in administrator mode and release configuration. The problem is reproducible by publishing the app with certain .NET 8.0 settings, launching it as an administrator on Windows 10 version 19041, and then attempting to pick a file, which unexpectedly causes the app to crash instead of functioning normally.
3. Global defined EventTriggers get triggered twice: This issue describes a problem where an EventTrigger defined globally in a style causes its invoke method to be called twice, resulting in duplicate event handling. The user notes that applying the same EventTrigger through a named style with a key triggers the invoke method only once, indicating a discrepancy in behavior between global and keyed style definitions across multiple platforms including iOS, Android, and Windows.
4. Path with ArcSegments is sporadically drawn offset from expected arc: This issue describes a sporadic rendering problem where arcs drawn using ArcSegment in PathFigure/PathGeometry appear slightly offset from their expected starting positions, particularly for large arcs greater than 180 degrees. The problem occurs across Windows, Android, and iOS platforms, becomes more frequent near the 180-degree threshold and with thicker strokes, and persists despite attempted workarounds such as using multiple smaller arcs or manually drawing arcs with LineSegments.
5. .NET Maui does not support FontAutoScalingEnabled for windows platform: This issue highlights that the .NET Maui framework does not properly support the FontAutoScalingEnabled property on the Windows platform, causing text labels to scale incorrectly when the display scaling is changed. Specifically, when FontAutoScalingEnabled is set to false, the text size still increases with higher display scaling settings, which should not occur according to the expected behavior.

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:

• Cross-platform UI inconsistencies: Several issues highlight inconsistent behavior across platforms, such as tap gesture recognizers attached differently on iOS/Mac versus Android/Windows causing event handling challenges, and UI elements like buttons or labels behaving differently in visibility or layout on iOS compared to Android and Windows. These inconsistencies complicate uniform app behavior and testing across supported platforms.
• issues/31609, issues/31644, issues/31674

• Layout and rendering problems: Multiple reports describe layout issues including content misalignment in ScrollView with RightToLeft flow direction on iOS/macOS, crashes due to LayoutCycleException on Windows with multiple CollectionViews, and navigation bar TitleView content overflow on iOS. These problems affect UI stability and visual correctness across different device configurations.
• issues/31610, issues/31627, issues/31688

• Performance and build optimization: There is a focus on improving performance by reducing generated Binding code to minimize runtime overhead, as well as addressing build warnings related to incorrect WinAppSDK version references during Windows builds. These issues aim to optimize both app runtime efficiency and build process correctness.
• issues/31614, issues/31668

• Platform-specific bugs and crashes: Several platform-specific bugs are reported, including an Android app popup loop after breakpoint resume, a crash caused by invalid CarouselView position on Android, and an intermittent IllegalArgumentException due to theme inheritance issues. These bugs cause app instability and require platform-targeted fixes.
• issues/31626, issues/31680, issues/31703

• Windows-specific UI and behavior issues: Windows platform problems include incorrect scrolling behavior when updating CurrentItem in CollectionView, inconsistent close button positioning on different Windows 10 machines, and AutomationId detection failure for IndicatorView during UI automation testing. These issues impact user experience and automated testing on Windows.
• issues/31642, issues/31666, issues/31670

• BlazorWebView and hybrid app enhancements: Issues include HotReload failures in Blazor MAUI hybrid projects on Windows due to XML serialization errors, and a feature request to prevent BlazorWebView from launching external browsers on new window requests, enabling better in-app web content control. These affect developer productivity and app integration capabilities.
• issues/31633, issues/31634

• DateTime and localization issues: An Android-specific problem where changing the device's 24-hour format setting does not update the app's CurrentCulture.DateTimeFormat, causing incorrect time display, highlights challenges in reflecting user locale preferences dynamically.
• issues/31640

• WebView and network request enhancements: A request to expose the request body in the WebResourceRequested event aims to enable advanced scenarios like extracting authentication tokens, improving WebView capabilities in .NET MAUI.
• issues/31652

• TimePicker and orientation handling: On Android, the TimePicker dialog fails to redraw correctly upon device rotation, leading to improper layout and user experience issues in different screen orientations.
• issues/31658

• Testing coverage and quality assurance: There is a call for more comprehensive testing of Windows Image Aspect handling fixes, covering various image alignments, sizes, container constraints, and dynamic resizing to ensure robustness and performance.
• issues/31686

• Device identification and licensing challenges: Implementing a reliable per-device licensing model is difficult due to the lack of a consistent unique device identifier across user profiles, reinstallations, and resets, prompting inquiries about adding such support in MAUI.
• issues/31687

• Navigation and UI regression on iOS: A regression in .NET MAUI iOS navigation page causes the TitleView content to overflow and be clipped outside device bounds, indicating a recent change introduced unwanted margin behavior.
• issues/31671

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

Summarized Issues:

• Application crashes due to accessibility properties regression: A regression in .NET MAUI version 9.0.110 on Windows causes the application to crash with a System.InvalidCastException when a ToolbarItem has a non-empty SemanticProperties.Description set. This issue did not occur in version 9.0.100 and can be avoided by downgrading or not using accessibility properties for ToolbarItems.
• issues/31606

• Static asset handling in Blazor Maui Web template: The Blazor Maui Web template requires updating by removing the call to UseStaticFiles() in Program.cs and adding a call to MapStaticAssets before MapRazorComponents. This change is necessary to properly handle static assets in the application.
• issues/31617

• File picker displays unsupported file types as selectable on MacCatalyst: On MacCatalyst, the Microsoft.Maui.Storage.IFilePicker shows certain file types like .bin and .zip as greyed out but still selectable, which causes user confusion. This behavior affects the clarity of file selection in the picker UI.
• issues/31620

• MSAL integration issues on Windows due to missing WebView2 assembly: Integrating MSAL with .NET MAUI and Azure Entra ID on Windows fails because the required Microsoft.Web.WebView2 assembly is missing or incompatible, leading to build and runtime errors that block user authentication. Workarounds include switching to the Microsoft.Identity.Client.Desktop.WinUI3 package and modifying platform-specific window handle code.
• issues/31621

• Android support and dependency compatibility for .NET MAUI .NET 9: .NET MAUI .NET 9 supports Android devices with a 16 KB page size, but developers need guidance on handling dependencies that may not yet be compatible with this configuration. This clarification helps ensure proper support for newer Android device architectures.
• issues/31691

• Android project property loading error due to incorrect AndroidPackageFormat values: A .NET MAUI Android project encounters a System.ArgumentException because the AndroidRule::AndroidPackageFormat property expects 4 values but only receives 2. Temporarily removing a specific MauiXaml item group from the project file resolves the issue in the editor.
• issues/31700

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. Candidate Branch September 22nd: This pull request consolidates multiple fixes, optimizations, and extensive UI test cases across various controls and platforms in the .NET MAUI project, including improvements to gradient rendering, navigation behavior, exception handling, and feature matrix tests for controls like RefreshView, TwoPaneView, WebView, SwipeView, Border, FlyoutPage, ContentPage, Shapes, NavigationPage, and more, targeting the main branch as a candidate branch update for September 22nd.

• URL: pull/31681

• Merged: No

• Associated Commits: 7b5fe, 79bb2, 174a3, adf42, 02363, cca82, 028fe, a41a0, b4b82, 60310, cd9ba, 71602, 858be, 466ee, 7978f, 8e150, 5ce35, 86559, e00fa, 0f237, 9afc9, 28387, a0f2c, ed532, 87c08, ff11f, 2f465, 5a97b, bc9e9, 56e93, 655b4, e0f35

2. Net10 main merge: This pull request aims to merge changes from the net10 branch into the main branch of the .NET MAUI repository, including numerous fixes, test enhancements, CI pipeline updates, and template improvements to ensure stability and alignment with the main development line.

• URL: pull/31699

• Merged: No

• Associated Commits: 09238, c45a6, d9354, 2cd6c, ee26a, 4b0e0, 893bb, 45368, 8798e, 5a071, 9611f, 3273d, 26059, 9d75f, 3cc91, 8b1ee, 84e34, 01c89, 1c63c, db83d, 31939

3. [XSG] Simplify ColorConverter: This pull request simplifies the ColorConverter by moving parsing and conversion logic from the Color class to ColorUtils for shared use between Graphics and SourceGen projects, leveraging ChangeColor.TryParse to handle all supported formats efficiently, and updating the source generator to dynamically scan public static fields of the Colors class instead of maintaining a separate list of known colors.

• URL: pull/31660

• Merged: No

• Associated Commits: 016ca, 42fce, 097a2, 65d08, 97739, 29043, d59d8, c523c, cb659, f29fe, 15630

Other Open Pull Requests

• CollectionView and Scrollable Headers on Android: This topic includes fixes to enable scrollable content within the CollectionView.Header on Android by modifying touch event handling in ItemContentView. Additionally, it addresses an ArgumentOutOfRangeException when reordering items to the last index in a CollectionView with a Header by adjusting index calculations to account for header offsets.
  • pull/31661, pull/31639

• Windows and Image Aspect Handling Tests: These pull requests add comprehensive tests to verify fixes related to image aspect handling on Windows, covering various alignments, size constraints, and mixed aspect ratios. They also reintroduce and expand UI test cases for image processing issues, focusing on downsizing, flipping, rotation, and exceptions on iOS.
  • pull/31694, pull/31665

• iOS WebView JavaScript Evaluation Fixes: This topic covers fixes to the iOS WebView's EvaluateJavaScriptAsync() method to handle different NSObject result types properly, including JSON serialization for complex objects. Extensive tests were added to ensure consistent JavaScript evaluation behavior across platforms.
  • pull/31647

• MAUI Blazor Template Modernization: This pull request updates the MAUI Blazor templates to achieve parity with the latest ASP.NET Core Blazor templates by modernizing Bootstrap assets, aligning Razor components and routing, enhancing accessibility, and adding missing files like favicons and JavaScript bundles. The changes ensure generated applications match ASP.NET Core in functionality and developer experience.
  • pull/31684

• WinUI ScrollView Shutdown Fix: This fix prevents the ScrollView height from increasing after app closure by changing the shutdown sequence to set the root view content to null before clearing the toolbar, avoiding unnecessary layout updates during shutdown.
  • pull/31695

• Accessibility Improvements on iOS: Enhancements include adding AccessibilityLabel and AccessibilityValue properties to the Shell Flyout's UITableViewController to enable VoiceOver to properly announce the flyout. These changes improve accessibility by replacing generic table identification with meaningful descriptions.
  • pull/31619

• ScrollView and Map Feature Matrix Enhancements: These pull requests reintroduce and expand interactive testing and configuration pages for ScrollView child layout options and map controls. They add new UI pages, MVVM view models, and interactive elements targeting iOS and macOS platforms to facilitate layout control and map behavior testing.
  • pull/31650, pull/31656

• UITest Updates and Emulator Support: This topic includes reopening and completing UITest updates with new SafeAreaEdges categories, adding support for Pixel 9 / API 36 emulator configurations, and updating screenshot cropping logic. It also covers UI test pipeline enhancements for Android API 36 with improved test filtering and device configuration.
  • pull/31655, pull/31631

• Shape and Rectangle Rendering Fixes: Fixes address issues where BoxView inside AbsoluteLayout on iOS/macOS failed to return to AutoSize after explicit bounds reset, and where small non-integer height rectangles rendered as thin stroked lines instead of filled shapes. These changes ensure consistent rendering behavior across multiple platforms.
  • pull/31648, pull/31651

• Android CarouselView Scroll Position Fix: This fix corrects the Android CarouselView behavior where resetting the data source and updating the CurrentItem to the last item failed to visually scroll to that item. It adjusts scroll position calculations and ensures proper virtual positioning and centering in loop mode.
  • pull/31672

• Branch Merge and Sample App Enhancements: These pull requests update the net10.0 branch with the latest main branch changes resolving merge conflicts and enhance the maui-mobile developer sample by incorporating updates and fixing a null exception related to ScrollView to CollectionView changes.
  • pull/31693, pull/31646

• UITest Reliability and Refactoring on MacCatalyst: This update renames button variables and AutomationId properties for clarity, removes conditional test failure directives, and refactors test steps to improve UITest reliability in CI environments despite unresolved failure causes.
  • pull/31653

• ChangeEnum Source Generator Bug Fix: This fix corrects a bug in the ChangeEnum source generator that caused invalid code with duplicated namespaces in enum conversions by generating proper code without repeating the namespace.
  • pull/31702

• Build Warning Resolution for WinAppSDK: This pull request eliminates build warnings caused by repeated import of Microsoft.Build.Msix.props by ensuring the build process no longer references WinAppSDK 1.6 in older projects.
  • pull/31669

• Catalyst Test Runner Rework: The Catalyst test runner was reworked to enable launching tests directly via startup arguments instead of UI navigation by adding environment variable support, dynamic test page creation, enhanced lifecycle management, and updated helper methods for streamlined test execution.
  • pull/31673

• Package Version Updates: This update moves Microsoft.Extensions and Microsoft.AspNetCore Core dependencies from version 9.0.8 to 9.0.9 in the eng/Versions.props file, incorporating the latest minor releases, bug fixes, and updated Emscripten workload components.
  • pull/31697

• iOS NavigationPage TitleView Layout Fix: This fix addresses TitleView content overflow on iOS by replacing a custom method with an override of AlignmentRectInsets that respects the IView.Margin property. It preserves native margins by default to prevent layout regressions while allowing negative margins for precise alignment.
  • pull/31701

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

Key Closed Pull Requests

1. Update the Windows App SDK to 1.8: This pull request proposes updating the Windows App SDK to the stable version 1.8, building upon a previous pull request and addressing issue #30858, but it has not been merged yet.

• URL: pull/31615

• Merged: No

• Associated Commits: b30de, f07ec, 555dc, c221b

2. Fix Aspire ServiceDefaults project template naming: This pull request fixes a naming issue in the .NET MAUI Aspire Service Defaults project template by updating the template configuration to use consistent and correct project file names and adds an integration test to verify that the template generates correctly named project files for various input names.

• URL: pull/31616

• Merged: Yes

• Associated Commits: 3cf11, eb6a0, 97a6e

3. [Windows] Revert cleanup of AccessibilityExtensions: This pull request reverts a previous cleanup of the AccessibilityExtensions on Windows to fix a regression, while also adding a test to prevent similar issues in future pull requests.

• URL: pull/31608

• Merged: Yes

• Associated Commits: 554ac, 5742c

Other Closed Pull Requests

• UI Test Image Failures and Stability Improvements: Multiple pull requests address UI test image failures across different branches by updating snapshots, modifying flaky test cases, and improving rendering and test stability on various platforms. These changes enhance the reliability of UI tests and reduce intermittent failures in the test suite.
  • pull/31632, pull/31611, pull/31645, pull/31696

• Null Reference Exception Fixes: Two pull requests fix null reference exceptions by adding null checks and null-conditional operators in critical code paths, ensuring safer access to platform views and system resource providers. These fixes prevent runtime crashes and improve code robustness.
  • pull/31603, pull/31605

• Blazor Maui Web Template Middleware Updates: Several pull requests update the Blazor Maui Web template by replacing the legacy UseStaticFiles() middleware with the modern MapStaticAssets() middleware to improve static asset serving and integration with ASP.NET Core routing. These changes include a revert and a reland to ensure the correct application of the update.
  • pull/31618, pull/31676, pull/31677

• Reverts and CI Stability: Multiple pull requests revert previous changes due to continuous integration failures or because issues were resolved by other fixes, aiming to maintain branch stability and prepare for future re-integration of those changes.
  • pull/31643, pull/31692

• Performance and Code Optimization: A pull request optimizes code by avoiding multiple enumerations of a collection, improving performance in the affected area. This change addresses a specific issue to enhance efficiency.
  • pull/31622

• XAML Compilation and Source Generation Fix: One pull request fixes missing boilerplate code generation for ResourceDictionary when using the global XML namespace, restoring related performance improvements in XAML compilation and source generation.
  • pull/31623

• Pull-to-Refresh Test Stability Enhancements: A pull request improves the flaky pull-to-refresh test by adding a retry mechanism, refining swipe parameters, and enhancing verification to ensure the test only passes when refresh completes successfully.
  • pull/31625

• Markup Node Line Information Correction: One pull request corrects line information transfer when expanding markup nodes, improving #line pragmas and VisualDiagnostics, and fixes a related issue.
  • pull/31641

• Windows App SDK Upgrade: A pull request upgrades the Windows App SDK from version 1.7.3 to 1.7.4, including fixes such as the resolution of a known issue in the microsoft-ui-xaml repository.
  • pull/31667

• Compilation Issue Fix: One pull request resolves a compilation issue by adding a missing comma in a list within a test case, ensuring correct syntax and successful build.
  • pull/31675

• Project Template Naming Consistency: A pull request introduces a new .NET MAUI for .NET Aspire Service Defaults project template that correctly applies custom project naming by configuring the template’s sourceName, resolving previous naming inconsistencies in generated .csproj files and namespaces.
  • pull/31612

• iOS Shell Flyout Header Layout Adjustment: One pull request introduces a method to adjust the header's content inset in the iOS Shell flyout based on FlyoutHeaderBehavior, ensuring correct layout and scroll behavior.
  • pull/31607

• Test Fixes and Updates: Individual pull requests fix specific test cases such as "CurrentItemShouldWork" and add missing snapshots to improve test accuracy and stability.
  • pull/31685, [pull/31696](https://github.com/pull/31696]

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.

Contributor	Commits	Pull Requests	Issues	Comments
Copilot	56	11	0	148
jfversluis	66	4	0	43
jsuarezruiz	45	7	1	36
kubaflo	56	8	0	9
StephaneDelcroix	33	7	1	24
NafeelaNazhir	26	8	4	20
devanathan-vaithiyanathan	44	5	1	2
rmarinho	42	4	0	2
MartyIX	24	6	1	4
HarishKumarSF4517	18	3	1	13