Skip to content

July 13th, Candidate - #36411

Merged
kubaflo merged 142 commits into
mainfrom
inflight/candidate
Aug 10, 2026
Merged

July 13th, Candidate#36411
kubaflo merged 142 commits into
mainfrom
inflight/candidate

Conversation

@kubaflo

@kubaflo kubaflo commented Jul 6, 2026 •
edited by PureWeen
Loading

Copy link
Copy Markdown
Contributor

What's Coming

.NET MAUI inflight/candidate introduces significant improvements across all platforms with focus on quality, performance, and developer experience. This release includes 110 commits with various improvements, bug fixes, and enhancements.

Activityindicator

Animation

Blazor

BlazorWebView

Border

CollectionView

🔧 Fixes

Core Lifecycle

Datepicker

Drawing

Editor

Entry

Essentials

Filepicker

Flyoutpage

General

Gestures

Hybridwebview

Label

Layout

Map

Menubar

Navigation

Picker

RadioButton

Refreshview

SafeArea

ScrollView

Searchbar

Shapes

Shell

SwipeView

Templates

Titlebar

WebView

Window

Xaml

🔧 Fixes
🔧 Infrastructure (6)
🧪 Testing (3)
📦 Other (5)
📝 Issue References

Fixes #4715, Fixes #6016, Fixes #8680, Fixes #11764, Fixes #13323, Fixes #14894, Fixes #16119, Fixes #19667, Fixes #20586, Fixes #22326, Fixes #22507, Fixes #22634, Fixes #22642, Fixes #22683, Fixes #23023, Fixes #23315, Fixes #24533, Fixes #25689, Fixes #28064, Fixes #29066, Fixes #29131, Fixes #29421, Fixes #29898, Fixes #30081, Fixes #30248, Fixes #30515, Fixes #31065, Fixes #31808, Fixes #31824, Fixes #31892, Fixes #32059, Fixes #32221, Fixes #32271, Fixes #32275, Fixes #32435, Fixes #32724, Fixes #32796, Fixes #32832, Fixes #32987, Fixes #33103, Fixes #33110, Fixes #33307, Fixes #33785, Fixes #33833, Fixes #34100, Fixes #34103, Fixes #34257, Fixes #34307, Fixes #34318, Fixes #34422, Fixes #34462, Fixes #34536, Fixes #34931, Fixes #35042, Fixes #35216, Fixes #35386, Fixes #35410, Fixes #35471, Fixes #35490, Fixes #35564, Fixes #35571, Fixes #35572, Fixes #35583, Fixes #35613, Fixes #35650, Fixes #35675, Fixes #35700, Fixes #35736, Fixes #35752, Fixes #35753, Fixes #35755, Fixes #35761, Fixes #35764, Fixes #35771, Fixes #35785, Fixes #35788, Fixes #35795, Fixes #35796, Fixes #35806, Fixes #35809, Fixes #35837, Fixes #35839, Fixes #35844, Fixes #35859, Fixes #35860, Fixes #35862, Fixes #35902, Fixes #35943, Fixes #36010, Fixes #36015, Fixes #36018, Fixes #36032, Fixes #36033, Fixes #36035, Fixes #36059, Fixes #36154, Fixes #36173

Copilot AI review requested due to automatic review settings July 6, 2026 15:32
@kubaflo
kubaflo temporarily deployed to copilot-pat-pool July 6, 2026 15:32 — with GitHub Actions Inactive
Copilot AI reviewed Jul 6, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🚀 Dogfood this PR with:

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

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

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 36411"

@kubaflo
kubaflo temporarily deployed to copilot-pat-pool July 6, 2026 15:33 — with GitHub Actions Inactive
@kubaflo
kubaflo temporarily deployed to copilot-pat-pool July 6, 2026 15:33 — with GitHub Actions Inactive
@kubaflo
kubaflo temporarily deployed to copilot-pat-pool July 6, 2026 15:39 — with GitHub Actions Inactive
@kubaflo
kubaflo temporarily deployed to copilot-pat-pool July 6, 2026 15:40 — with GitHub Actions Inactive
@github-actions github-actions Bot added area-controls-general General issues that span multiple controls, or common base classes such as View or Element platform/android platform/ios platform/macos macOS / Mac Catalyst platform/windows labels Jul 6, 2026
@kubaflo
kubaflo temporarily deployed to copilot-pat-pool July 6, 2026 15:40 — with GitHub Actions Inactive
@kubaflo
kubaflo force-pushed the inflight/candidate branch from 4c111a3 to 86758bd Compare July 6, 2026 16:12
@github-actions github-actions Bot mentioned this pull request Jul 7, 2026
Closed
@TamilarasanSF4853 TamilarasanSF4853 mentioned this pull request Jul 7, 2026
Merged
sheiksyedm pushed a commit that referenced this pull request Jul 7, 2026
@TamilarasanSF4853
[Testing] Fixed Build error on inflight/ candidate PR 36411 (#36424)
9aee358 
The build fails in the candidate PR
#36411, so this PR removes the APIs
due to the fix commit
https://github.com/dotnet/maui/pull/35154/changes#diff-55adeb4d1c5d77cb7fe1c355f585446544f7ac5d74094169a9468395a1bc3967L27,
which removes the method.
<img width="800" height="73" alt="image"
src="https://github.com/user-attachments/assets/4fbb35bb-d3dc-4f43-b9eb-043ce3d34762"
/>


Build Link -
https://dev.azure.com/dnceng-public/public/_build/results?buildId=1495447&view=logs&j=227beb21-2eda-5fca-23b0-55de6ad19261&t=fd3b17f4-9cb6-5188-4b56-657d9a0a6474

**Fixes:**
#36411
Copilot AI review requested due to automatic review settings July 7, 2026 08:13
Copilot AI reviewed Jul 7, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

@github-actions github-actions Bot mentioned this pull request Jul 7, 2026
Closed
KarthikRajaKalaimani and others added 9 commits July 7, 2026 04:27
@KarthikRajaKalaimani
Fix MauiView leaks detached platform views when SafeAreaEdges include…
a7c14fa 
…s SoftInput (#35586)

<!-- Please let the below note in for people that find this PR -->
> [!NOTE]
> Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
Thank you!

### Issue Details:

Every MauiView that uses SafeAreaEdges.SoftInput stays alive in memory
after being removed from the screen. Users saw platform=12/12 views
never getting released in iOS and Mac platform.
       
### Root Cause:

When a MAUI view is configured with SafeAreaEdges.SoftInput on iOS or
MacCatalyst, MauiView.SubscribeToKeyboardNotifications() registers two
observers with NSNotificationCenter.DefaultCenter — one for
UIKeyboard.WillShowNotification and one for
UIKeyboard.WillHideNotification. Each call to AddObserver returns an
NSObject token that the notification center holds strongly. Because the
callbacks (OnKeyboardWillShow, OnKeyboardWillHide) are instance methods,
the delegate objects capture a strong reference to this — the MauiView
instance. This creates an unbroken retain chain: NSNotificationCenter →
NSObject token → delegate → MauiView. As long as those observer tokens
are registered, the notification center transitively keeps every
subscribed MauiView alive, regardless of whether the view has been
removed from the visual tree, its handler disconnected, and all
MAUI-side references dropped.
 
The reason the tokens were never removed on detach comes down to a
single guard condition in UpdateKeyboardSubscription(). The method was
structured as if (Window != null) { ... }, meaning all subscription
management — both subscribe and unsubscribe — was gated on the view
being attached to a window. When MovedToWindow() fires with Window ==
null (the standard UIKit signal that a view has been removed from the
hierarchy), UpdateKeyboardSubscription() was called but immediately fell
through without doing anything. UnsubscribeFromKeyboardNotifications()
was never reached, leaving the observer tokens live in the notification
center indefinitely. The result, confirmed by the sandbox repro, was
platform=12/12 alive after 12 forced GC cycles for views using
SafeAreaEdges.SoftInput, versus platform=0/12 for the control case.

### Description of Change:

The fix flattens the conditional in UpdateKeyboardSubscription() so that
the else branch — which calls UnsubscribeFromKeyboardNotifications() —
fires for all cases where the view should not be actively subscribed,
including detach. The original nested structure if (Window != null) { if
(ShouldSubscribe) subscribe; else unsubscribe; } is replaced with if
(Window != null && ShouldSubscribeToKeyboardNotifications()) {
SubscribeToKeyboardNotifications(); } else {
UnsubscribeFromKeyboardNotifications(); }. Now when MovedToWindow()
fires with Window == null, the condition evaluates to false and
UnsubscribeFromKeyboardNotifications() is called, issuing
NSNotificationCenter.DefaultCenter.RemoveObserver(token) for both
keyboard observers. This severs the retain chain and allows the MauiView
to be collected normally by the GC. The change is 9 lines, touches a
single method, and introduces no new state or lifecycle hooks.

**Tested the behavior in the following platforms:**

- [x] Android
- [ ] Windows
- [x] iOS
- [ ] Mac

### Reference:

N/A

### Issues Fixed:

Fixes  #35386         

### Screenshots
| Before  | After  |
|---------|--------|
| <img
src="https://github.com/user-attachments/assets/cbbd452a-6565-4e0b-a17d-12c83204bfe5"
Width="400" Height="600"/> | <img
src="https://github.com/user-attachments/assets/3ebbeba2-9fd1-42ac-a4d5-06d5184f2cc7"
Width="400" Height="600"/> |

---------
@NafeelaNazhir
[Android][Testing] Add dedicated CI stage for SafeAreaEdges tests on …
1ada1c1 
…API 36 (Pixel 3 XL) (#31631)

>[!NOTE]
>Are you waiting for the changes in this PR to be merged?
>It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR->Builds) from
this PR and let us know in a comment if this change resolves your issue.
Thank you!

This pull request sets up a dedicated Android CI stage for SafeAreaEdges
UI tests, running on a notch-equipped device (Pixel 3 XL skin, Android
API 36). It is a continuation of
#31355.

**Android test pipeline changes (`ui-tests.yml`):**

- Moved `SafeAreaEdges` out of the standard Android test filter batch
into its own dedicated stage, so it no longer runs alongside other tests
on API 30 (which lacks a notch)
- Added a new `androidApiLevelsExtended: [36]` parameter to target
Android API 36 without changing the existing `androidApiLevels: [30]`
configuration
- Created a dedicated stage (`android_ui_tests_safeareaedges`) that runs
SafeAreaEdges tests on Android API 36 using the Pixel 3 XL device skin
(which has a notch/display cutout)

**Device skin support (`ui-tests-steps.yml`):**

- Added deviceType parameter to `ui-tests-steps.yml` to allow specifying
an Android emulator device skin
- When set, appends `--skin="<deviceType>"` to the test runner command,
selecting the correct AVD skin at emulator creation time

Note: This PR contains only the YAML pipeline updates and is a
continuation of [#31355](#31355)


Fixes #32059

---------
@HarishwaranVijayakumar
[Mac] Fix for DeviceDisplay.MainDisplayInfoChanged event not getting …
8e1d4a9 
…raised (#31786)

<!-- Please let the below note in for people that find this PR -->
> [!NOTE]
> Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
Thank you!

<!--
!!!!!!! MAIN IS THE ONLY ACTIVE BRANCH. MAKE SURE THIS PR IS TARGETING
MAIN. !!!!!!!
-->
### Issue Details

- When changing the resolution, rotation, or refresh rate, the
DeviceDisplay.MainDisplayInfoChanged event is not triggered.

### Root Cause of the issue

- DidChangeStatusBarOrientationNotification does not apply to Mac
Catalyst apps because they do not have a mobile-style status bar. On
desktop, changes such as resolution, refresh rate are not reported
through mobile-oriented notifications.

### Description of Change

**Mac Catalyst-specific display handling:**

* Added P/Invoke declarations for Core Graphics APIs in
`DeviceDisplay.ios.cs` to fetch display properties (resolution, refresh
rate, rotation) directly from the system, bypassing potentially stale
UIKit data.
* Updated `GetMainDisplayInfo()` to use Core Graphics APIs on Mac
Catalyst, including logic to calculate orientation and rotation based on
system-reported values.

**Display change event handling:**

* On Mac Catalyst, replaced status bar orientation notifications with
`NSApplicationDidChangeScreenParametersNotification` to reliably detect
display changes (resolution, refresh rate, etc.).

**Equality logic improvements:**

* Updated the `DisplayInfo.Equals()` method to include `RefreshRate` in
equality checks, ensuring all display properties are considered.

### Issues Fixed

<!-- Please make sure that there is a bug logged for the issue being
fixed. The bug should describe the problem and how to reproduce it. -->

Fixes #22634 
Fixes #22642

### Tested the behaviour in the following platforms

- [x] - Windows 
- [x] - Android
- [x] - iOS
- [x] - Mac

### Output
| Before | After |
|----------|----------|
| <video
src="https://github.com/user-attachments/assets/44c1c29a-b6d9-4231-b732-54d874d5ac7d">
| <video
src="https://github.com/user-attachments/assets/548ce40f-ee6f-4b7d-ac85-fa445e74f106">
|

<!--
Are you targeting main? All PRs should target the main branch unless
otherwise noted.
-->
@Dhivya-SF4094
Fixed Incorrect Window.Y and Window.Height values when closing a maxi…
bae509f 
…mized window (#29253)

### Issue Detail:
 
On the Windows platform, if the application window is maximized, the
main window X,Y values are in negative (-7, -7). For a non-maximized
window, values are correct.
 
### Root Cause
On Windows, when the application window is maximized, the values of
Window.Y and Window.Height reported during Window_Destroying are offset
by 8 pixels. This occurs because the default window bounds include the
non-client area (e.g., title bar and borders), which is excluded by the
OS when maximizing the window. As a result, the bounds do not accurately
reflect the actual client area used by the application, leading to
incorrect frame values being reported to the virtual view.
 
### Description of Change
To resolve this, the implementation now uses the Windows Desktop Window
Manager (DWM) API to retrieve the extended frame bounds via
DwmGetWindowAttribute with the DWMWA_EXTENDED_FRAME_BOUNDS attribute.
These bounds reflect the full screen-space dimensions of the window,
even when maximized.

In the UpdateVirtualViewFrame method, when the window is in a normal
state, the position and size reported by AppWindow are used directly.
When the window is maximized, the logic switches to use the bounds
provided by the DWM API. This ensures that the virtual view receives
accurate and consistent frame data (X, Y, Width, and Height) regardless
of the window state.

### Validated the behaviour in the following platforms
- [ ] Android
- [x] Windows
- [ ] iOS
- [ ] Mac
### Issues Fixed:
Fixes #29066
 
### Screenshots

| Before  | After |
|---------|--------|
|  <img
src="https://github.com/user-attachments/assets/3d5c192f-b681-491f-971a-6d6c0822ad12">
|  <img
src="https://github.com/user-attachments/assets/255b3ea5-c147-414d-9bce-6dbe119b4b2b"> 
|
@HarishKumarSF4517
[Testing] Refactoring Feature Matrix UITest Cases for RadioButton Con…
4a9f5db 
…trol (#35669)

> [!NOTE]
> Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
Thank you!

This pull request refactors and enhances the RadioButton feature matrix
test pages, focusing on improving the organization and functionality of
the options UI, as well as resetting the view model state more robustly.
The most significant changes are the restructuring of the options page
layout, the addition of a method to reset the RadioButton view model to
its defaults, and some minor test and code quality improvements.

**UI and Layout Improvements:**

* Refactored `RadioButtonOptionsPage.xaml` to group related numeric
options (Border Width, Character Spacing, Corner Radius, Font Size) into
a 2x2 grid for better organization and usability. Removed redundant
individual entry fields for these properties and adjusted row
assignments for all subsequent controls.
[[1]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224R38-R109)
[[2]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224L123-R194)
* Added a new "Font Auto Scaling" option as a pair of radio buttons,
replacing the previous font size entry field.
* Updated row indices throughout the options page to reflect the new
layout structure.
[[1]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224L61-R131)
[[2]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224L83-R153)
[[3]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224L97-R167)
[[4]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224L190-R215)
[[5]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224L217-R242)
[[6]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224L275-R306)
[[7]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224L296-R328)
[[8]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224L323-R355)
[[9]](diffhunk://#diff-28d48ddf94e5d659e0dd4bf27024b6333199e4c1cd7bcb22b4c6dce5d302e224L350-R383)

**ViewModel and State Management:**

* Added a `ResetToDefaults` method to `RadioButtonViewModel` to
centralize and standardize resetting all properties to their default
values.
* Updated the navigation handler in `RadioButtonControlMainPage` to use
the new `ResetToDefaults` method, ensuring consistent reset behavior
when navigating to the options page.

**Test and Code Quality:**

* Added the `[Category(UITestCategories.Material3)]` attribute to the
`Material3RadioButtonFeatureTests` class instead of individual test
methods for better test categorization.
[[1]](diffhunk://#diff-ba76e0d629a20f403900298a573a972756b9f6351185fa6b23171b77d988055aR12)
[[2]](diffhunk://#diff-ba76e0d629a20f403900298a573a972756b9f6351185fa6b23171b77d988055aL22-L30)
* Named the main radio button in `RadioButtonControlPage.xaml` as
`RadioButtonControlOne` for easier test referencing.

Issue Identified:
1. #35587
@SyedAbdulAzeemSF4852
[iOS/Mac Catalyst 26] Fix NavigationPage content not extending behind…
4f6367a 
… floating glass tab bar (#35523)

<!-- Please let the below note in for people that find this PR -->
> [!NOTE]
> Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
Thank you!

### Issue Details
- On iOS 26, pages inside a NavigationPage hosted in a TabbedPage do not
extend behind the new floating glass tab bar, leaving a white gap
between the page content and the tab bar.

### Root Cause
- On iOS 26, the tab bar changed from a solid bar to a floating glass
overlay. ParentingViewController.ViewWillAppear was assigning
EdgesForExtendedLayout = UIRectEdge.None for opaque navigation bars,
which prevented content from extending under the tab bar — leaving a
white gap between the page content and the new floating glass bar.

### Description of Change
- Updated NavigationRenderer to extend content layout behind the
floating tab bar when running on iOS/Mac Catalyst 26+ and the tab bar is
visible, preventing content from being clipped.

### Issues Fixed
Fixes #35490

### Validated the behaviour in the following platforms

- [ ] Windows
- [ ] Android
- [x] iOS
- [x] Mac

### Output
| Before | After |
|----------|----------|
| <video
src="https://github.com/user-attachments/assets/c4544467-6224-4dd4-bfd7-02c53bca3e8b">
| <video
src="https://github.com/user-attachments/assets/6c7186cd-3e42-4d9c-ad32-5f515a724991">
|
@SubhikshaSf4851
[Android] Fix MapHandler leaks when removed Pin instances are retaine…
bc75612 
…d by app code (#35686)

<!-- Please keep the note below for people who find this PR -->
> [!NOTE]
> Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment whether this change resolves your
issue. Thank you!
<!--
!!!!!!! MAIN IS THE ONLY ACTIVE BRANCH. MAKE SURE THIS PR IS TARGETING
MAIN. !!!!!!!
-->

This pull request improves the way map pin event subscriptions are
managed in the `MapHandler.Android` implementation. The main change is
to ensure that property change event handlers for map pins are only
attached once, and are properly cleaned up, preventing duplicate
subscriptions and potential memory leaks.
### Description of Change
**Pin subscription management improvements:**

* Introduced a `_subscribedPins` `HashSet<IMapPin>` field to track pins
that have event handlers attached, ensuring each pin is subscribed only
once.
* Updated the `AddPins` method to only add a property changed event
handler if the pin hasn't already been subscribed, using the
`_subscribedPins` set.
* Modified the `DisconnectPins` method to iterate over `_subscribedPins`
instead of the pin list, removing event handlers from only those pins
that were actually subscribed, and resetting the tracking set
afterwards.

### Regarding Tests : 
No automated device test included. MapView.OnCreate throws
IllegalStateException when no valid Google Maps API key is present —
even an empty string value fails. This is the same constraint that keeps
`MapTests.cs` behind #if IOS || MACCATALYST. Adding the key to
`AndroidManifest.xml `would expose credentials in the repo, which is not
acceptable.

<!-- Enter description of the fix in this section -->

### Issues Fixed

<!-- Please make sure that there is a bug logged for the issue being
fixed. The bug should describe the problem and how to reproduce it. -->

Fixes #35571 
### Tested the behavior in the following platforms

- [ ] Windows
- [x] Android
- [ ] iOS
- [ ] Mac

| Before Issue Fix | After Issue Fix |
|----------|----------|
| <video
src="https://github.com/user-attachments/assets/72bd098d-7a8f-4248-9ec3-7e30207eb6d4">
| <video
src="https://github.com/user-attachments/assets/703c227e-88b2-457c-b0a0-9e3bb5393da5">
|
<!--
Are you targeting main? All PRs should target the main branch unless
otherwise noted.
-->

---------
@jfversluis
Fix Android foreground geolocation update distance (#35783)
5741dd1 
<!-- Please let the below note in for people that find this PR -->
> [!NOTE]
> Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
Thank you!

### Description of Change

Stops Android foreground geolocation listening from using the desired
accuracy distance as the platform minimum movement threshold.
`MinimumTime` now controls the requested update cadence without imposing
a hidden 50m+ distance gate for `GeolocationAccuracy.Best`.

The existing accuracy value is still used by the listener to filter out
locations that do not satisfy the requested accuracy.

### Issues Fixed

Fixes #22683

### Validation

- Built `src/Essentials/src/Essentials.csproj` for
`net10.0-android36.0`.

### Manual regression coverage

Automated Android device coverage for this exact regression would
require controlling mock location updates from the test app/device
environment, which is not reliable in the current Essentials device-test
setup. Please validate the PR artifacts with the issue repro or
Essentials geolocation sample:

1. Install this PR's artifacts using the dogfood instructions above.
2. Start foreground listening with `new
GeolocationListeningRequest(GeolocationAccuracy.Best,
TimeSpan.FromSeconds(1))`.
3. Keep the app in the foreground and send or perform multiple location
changes that remain within 50 meters of the previous position.
4. Confirm `LocationChanged` continues firing for those sub-50m updates
instead of stopping after the initial GPS/network callbacks.
5. Confirm updates still include high-accuracy locations; locations
whose reported accuracy is worse than the requested accuracy can still
be filtered by the existing listener accuracy check.

---------
@prakashKannanSf3972
[Android] - Fix KeepScrollOffset Behavior During Dynamic Item Additio…
088aaf0 
…ns in CollectionView (#29255)

> [!NOTE]
> Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
Thank you!

### Issue Details 

`KeepScrollOffset` mode does not maintain scroll position when new items
are inserted into the CollectionView, resulting in unintended upward
scrolling.

### Root Cause 

When new items are added to the collection, the scroll offset is
recalculated based on the updated layout. This results in incorrect
offset adjustments, causing the scroll position to shift upward instead
of being correctly preserved.

### Description of Change

* Added `AddScrollListener` and `RemoveScrollListener` methods to manage
scroll listeners dynamically. Adjusted the `TrackOffsets` method to
ensure scroll offsets are only adjusted when the first item is reached,
ensuring accurate scroll behavior and preventing unintended upward
scrolling during dynamic item insertions.

### Issues Fixed

Fixes #29131 

* The Following [PR - 27153](#27153)
fixes the `KeepItemsInView` issue on Android.

**Tested the behaviour in the following platforms**

- [x] Android
- [x]  Windows
- [x]  iOS
- [x] Mac

### Output

| Before| After|
|--|--|
| <video
src="https://github.com/user-attachments/assets/5d258709-c128-4cc4-9a73-bf3ad32b1cc3">
| <video
src="https://github.com/user-attachments/assets/8b22544b-cbbd-4d97-a54a-4573ca0290d5">
|

---------
Copilot AI reviewed Aug 5, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

Copilot AI review requested due to automatic review settings August 5, 2026 13:00
Copilot AI reviewed Aug 5, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

@github-actions @HarishwaranVijayakumar
[inflight/candidate] [Android] Fix Shell singleton page rendering bla…
a75894b 
…nk when re-pushed after absolute route reset (#37113)

Backport of #36903 to inflight/candidate

/cc @kubaflo @HarishwaranVijayakumar

Co-authored-by: HarishwaranVijayakumar <harishwaran.vijayakumar@syncfusion.com>
Copilot AI review requested due to automatic review settings August 5, 2026 13:00
Copilot AI reviewed Aug 5, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

@github-actions @SyedAbdulAzeemSF4852 @kubaflo
[inflight/candidate] [Android] Fix ActivityIndicator remaining visibl…
5d5b2ba 
…e after IsRunning/IsVisible set to false (#37112)

Backport of #36748 to inflight/candidate

/cc @kubaflo @SyedAbdulAzeemSF4852

Co-authored-by: SyedAbdulAzeemSF4852 <syedabdulazeem.a@syncfusion.com>
Co-authored-by: Jakub Florkowski <42434498+kubaflo@users.noreply.github.com>
Copilot AI review requested due to automatic review settings August 5, 2026 13:01
Copilot AI reviewed Aug 5, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

@TamilarasanSF4853 @Ahamed-Ali
[Testing] Fixed Test case failure in PR 36411 - [07/13/2026] Candidat…
fe972a8 
…e - 2 (#36935)

This PR addresses the test failures that occurred in the
inflight/candidate branch: #36411,
and includes updates to improve rendering and test stability across
platforms.

**Images:**

- Added base images and valid, re-saved images for the iOS and Mac
platforms.

Fixes: #36411

---------

Co-authored-by: Ahamed-Ali <102580874+Ahamed-Ali@users.noreply.github.com>
Copilot AI review requested due to automatic review settings August 6, 2026 14:24
Copilot AI reviewed Aug 6, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

@kubaflo

kubaflo commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

azure-pipelines Bot commented Aug 6, 2026

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).

@kubaflo
[inflight/candidate] Fix NullReferenceException in ApplyBindings when…
ffef47d 
… DefaultValueCreator mutates other BindableProperties (#37189)

<!-- Please let the below note in for people that find this PR -->
> [!NOTE]
> Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
Thank you!

Backport of #37148 to `inflight/candidate`.

The source PR included unrelated `inflight/current` branch-history
commits, so this backport cherry-picks only the functional fix commit
and its regression test.
Copilot AI review requested due to automatic review settings August 7, 2026 13:27
Copilot AI reviewed Aug 7, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

@Ahamed-Ali
Fix candidate SafeArea Edge lane and flaky failures (#37184)
7a2219b 
<!--
!!!!!!! MAIN IS THE ONLY ACTIVE BRANCH. MAKE SURE THIS PR IS TARGETING
MAIN. !!!!!!!
-->

### Description of Changes
- Enabled the **SafeAreaEdge** category to run on the iOS platform. It
was previously excluded due to the changes introduced in #31631
(categoryGroupsToTest). The SafeAreaEdge category has now been added to
the common lanes.
- Added the Issue32275 iOS 18.5 baseline images.
- Updated the baseline image for **VerifyFlyoutWithHeaderFooter**
(Issue32275). This test was introduced in #33335, and its baseline image
changed after the fix was reverted in #36495, so the screenshot has been
re-saved.

### Flaky Test Changes
- **LayoutShouldBeCorrectOnFirstNavigation** – Added a small test change
to improve the stability of this flaky test.
- **VerifyDefaultScrollToRequested** – Removed the VerifyScreenshot call
because the existing assertion is sufficient to validate the test.
Copilot AI review requested due to automatic review settings August 7, 2026 13:36
Copilot AI reviewed Aug 7, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

@kubaflo

kubaflo commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

azure-pipelines Bot commented Aug 7, 2026

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).

@kubaflo

kubaflo commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

/azp run maui-pr-devicetests

@azure-pipelines

azure-pipelines Bot commented Aug 7, 2026

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

@build-analysis build-analysis Bot mentioned this pull request Aug 7, 2026
Open
3 tasks
@kubaflo kubaflo mentioned this pull request Aug 10, 2026
Open
@kubaflo
kubaflo merged commit abf61c2 into main Aug 10, 2026
198 checks passed
@kubaflo
kubaflo deleted the inflight/candidate branch August 10, 2026 16:55
@github-actions github-actions Bot added this to the .NET 10 SR10 milestone Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment