Skip to content

[iOS] Fix: ActivityIndicator IsRunning ignores IsVisible when set to true#28983

Merged
kubaflo merged 9 commits intodotnet:inflight/currentfrom
bhavanesh2001:fix_28968
Mar 5, 2026
Merged

[iOS] Fix: ActivityIndicator IsRunning ignores IsVisible when set to true#28983
kubaflo merged 9 commits intodotnet:inflight/currentfrom
bhavanesh2001:fix_28968

Conversation

@bhavanesh2001
Copy link
Copy Markdown
Contributor

@bhavanesh2001 bhavanesh2001 commented Apr 14, 2025

Description of Change

On iOS, the ActivityIndicator becomes visible even when IsVisible = false and IsRunning = true, effectively ignoring the IsVisible property.

Root Cause

Visibility is not being correctly mapped in iOS.

By default, IsVisible is true for all elements, so we must explicitly manage visibility based on the IsRunning value — especially since it's expected that the ActivityIndicator is hidden by default.

The current implementation seems to work because IsRunning defaults to false, which calls StopAnimating() and hides the native control. However, if HidesWhenStopped is set to false, the control remains visible without animating — which is incorrect.

To fix this, we explicitly update the visibility inside the IsRunning mapper, just as it's done on Android.

Before Fix After Fix
before_fix.mov
after_fix.mov

Issues Fixed

Closes #28968

@bhavanesh2001 bhavanesh2001 requested a review from a team as a code owner April 14, 2025 19:06
@dotnet-policy-service dotnet-policy-service bot added the community ✨ Community Contribution label Apr 14, 2025
@bhavanesh2001
Copy link
Copy Markdown
Contributor Author

  <VerticalStackLayout VerticalOptions="Center" HorizontalOptions="Center"> 
                <ActivityIndicator HorizontalOptions="Center" x:Name="busy"> 
                    <ActivityIndicator.Triggers>
                        <DataTrigger TargetType="ActivityIndicator" 
                            Binding="{Binding Source={x:Reference isRunningSwitch}, Path=IsToggled}" 
                            Value="True">
                             <Setter Property="IsRunning" Value="True" />
                        </DataTrigger>
                        <DataTrigger TargetType="ActivityIndicator" 
                            Binding="{Binding Source={x:Reference isVisibleSwitch}, Path=IsToggled}" 
                            Value="True"> 
                            <Setter Property="IsVisible" Value="True" /> 
                        </DataTrigger> 
                        <DataTrigger TargetType="ActivityIndicator" 
                            Binding="{Binding Source={x:Reference isRunningSwitch}, Path=IsToggled}" 
                            Value="False"> 
                            <Setter Property="IsRunning" Value="False" /> 
                        </DataTrigger> 
                        <DataTrigger TargetType="ActivityIndicator" 
                            Binding="{Binding Source={x:Reference isVisibleSwitch}, Path=IsToggled}" 
                            Value="False"> <Setter Property="IsVisible" Value="False" /> 
                        </DataTrigger> 
                    </ActivityIndicator.Triggers> 
                </ActivityIndicator> 
                <Switch x:Name="isRunningSwitch" HorizontalOptions="Center" /> 
                <Label Text="Toggle IsRunning" HorizontalOptions="Center" /> 
                <Switch x:Name="isVisibleSwitch" IsToggled="True" HorizontalOptions="Center" /> 
                <Label Text="Toggle IsVisible" HorizontalOptions="Center" />
</VerticalStackLayout>

Copy link
Copy Markdown
Contributor

@jsuarezruiz jsuarezruiz left a comment

Choose a reason for hiding this comment

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

Could you include a Device Test for iOS checking the IsAnimating property of the UIActivityIndicatorView using the ActivityIndicator IsRunning and IsVisible properties? https://github.com/dotnet/maui/blob/ef1ec07908eda7b7bf9979fbbf9c374fbe7f2acf/src/Core/tests/DeviceTests/Handlers/ActivityIndicator/ActivityIndicatorHandlerTests.iOS.cs

@Domik234
Copy link
Copy Markdown

Thanks a lot for this PR!

I just wanted to ask if you also tried using HidesWhenStopped = false on construction to leave Hidden attribute control onto developer? I'm asking with regard to the need to call into Obj-C rather than using a managed object (I am not sure how costly is this process).

Thanks for your time. 😀

@bhavanesh2001
Copy link
Copy Markdown
Contributor Author

bhavanesh2001 commented Apr 16, 2025

@Domik234 As I mentioned. HidesWhenStopped = false will result in a visible activity indicator by default ,but it wont animate(wont spin). This is not expected.

@Domik234
Copy link
Copy Markdown

@bhavanesh2001 Sorry, I was hasty. I was re-reading if I didn't missed and before I was able to edit, you answered. 😀

@bhavanesh2001
Copy link
Copy Markdown
Contributor Author

@jfversluis Could you run pipelines.

@jfversluis
Copy link
Copy Markdown
Member

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 3 pipeline(s).

public partial class ActivityIndicatorHandlerTests : CoreHandlerTestBase<ActivityIndicatorHandler, ActivityIndicatorStub>
{
#if !WINDOWS // On Windows, the platform control will return IsActive as true even when the control is not visible.
[Theory(DisplayName = "IsRunning Should Respect IsVisible")]
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Everything works as expected . But GetNativeIsRunning() seems to return true even when control is not visible. The UI test already covers this scenario.

Screen.Recording.2025-04-17.082414.mp4

@devanathan-vaithiyanathan
Copy link
Copy Markdown
Contributor

@bhavanesh2001 , Adding the fix in the below places appears to resolve the issue with minimal code changes. Do you think more code changes are necessary?
image

@bhavanesh2001
Copy link
Copy Markdown
Contributor Author

bhavanesh2001 commented Apr 17, 2025

@bhavanesh2001 , Adding the fix in the below places appears to resolve the issue with minimal code changes. Do you think more code changes are necessary? image

I think It's necessary to map and handle Visiibility like I did in the PR changes

#if __ANDROID__ || IOS || MACCATALYST
			// Since Visibility and IsRunning are dependent on each other, we handle Visibility explicitly.
			[nameof(IActivityIndicator.Visibility)] = MapIsRunning,
#endif

Based on the above changes, I think if I initialize the ActivityIndicator with IsVisible = false and IsRunning = true, and later change IsVisible to true, the indicator won't be shown (or it will be shown but wont animate)—even though at that point both IsVisible and IsRunning are true.

You can test and experiment with IsVisible and IsRunning using the sample code I included in the initial comments.

@devanathan-vaithiyanathan
Copy link
Copy Markdown
Contributor

@bhavanesh2001 , Adding the fix in the below places appears to resolve the issue with minimal code changes. Do you think more code changes are necessary? image

I think It's necessary to map and handle Visiibility like I did in the PR changes

#if __ANDROID__ || IOS || MACCATALYST
			// Since Visibility and IsRunning are dependent on each other, we handle Visibility explicitly.
			[nameof(IActivityIndicator.Visibility)] = MapIsRunning,
#endif

Based on the above changes, I think if I initialize the ActivityIndicator with IsVisible = false and IsRunning = true, and later change IsVisible to true, the indicator won't be shown (or it will be shown but wont animate)—even though at that point both IsVisible and IsRunning are true.

You can test and experiment with IsVisible and IsRunning using the sample code I included in the initial comments.

Yes @bhavanesh2001 , the mentioned scenario is working fine with my fix. The StartAnimate method is being called from the LayoutSubviews
Here is the demo video

ActivityIndicatorDemo.mov

@bhavanesh2001
Copy link
Copy Markdown
Contributor Author

@devanathan-vaithiyanathan I think with my changes, we can remove the animation logic from LayoutSubviews. Also, I tried to follow the approach we're already using in the Android case. But feel free to open a PR with your changes as an alternative to this one, so the team can choose the approach they'd prefer to go with.

@bhavanesh2001
Copy link
Copy Markdown
Contributor Author

/rebase

@jingo0
Copy link
Copy Markdown

jingo0 commented May 25, 2025

@bhavanesh2001 Will this be addressed in .NET 9, or is it planned for .NET 10?

@bhavanesh2001
Copy link
Copy Markdown
Contributor Author

@bhavanesh2001 Will this be addressed in .NET 9, or is it planned for .NET 10?

@jingo0 I'm not sure, But if you're facing an issue due to this, you can easily work your way around it.

You can bind IsVisible and IsEnabled to one property so that it hides and shows without any issues.

@jingo0
Copy link
Copy Markdown

jingo0 commented May 28, 2025

@bhavanesh2001 Will this be addressed in .NET 9, or is it planned for .NET 10?

@jingo0 I'm not sure, But if you're facing an issue due to this, you can easily work your way around it.

You can bind IsVisible and IsEnabled to one property so that it hides and shows without any issues.

Binding IsRunning to IsVisible property did the trick. Surprisingly this issue only occurs on few Views!

@ghost
Copy link
Copy Markdown

ghost commented Oct 15, 2025

Thanks for the patch — any update on merge status or further changes needed to get this landed? @jsuarezruiz @StephaneDelcroix

@development-jantar
Copy link
Copy Markdown

@jfversluis I think this is all done, just review is needed. Any chance this could be in next SR for MAUI?

@jfversluis
Copy link
Copy Markdown
Member

/rebase

@kubaflo kubaflo added the s/agent-fix-win AI found a better alternative fix than the PR label Mar 3, 2026
@dotnet dotnet deleted a comment from rmarinho Mar 3, 2026
@kubaflo kubaflo added the s/agent-changes-requested AI agent recommends changes - found a better alternative or issues label Mar 3, 2026
@PureWeen PureWeen modified the milestones: .NET 10 SR5, .NET 10 SR6 Mar 3, 2026
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 3, 2026

🚀 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 -- 28983

Or

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

@kubaflo kubaflo added s/agent-review-incomplete AI agent could not complete all phases (blocker, timeout, error) s/agent-fix-pr-picked AI could not beat the PR fix - PR is the best among all candidates s/agent-fix-win AI found a better alternative fix than the PR and removed s/agent-changes-requested AI agent recommends changes - found a better alternative or issues s/agent-fix-win AI found a better alternative fix than the PR labels Mar 4, 2026
@kubaflo kubaflo changed the base branch from main to inflight/current March 5, 2026 00:32
@kubaflo kubaflo merged commit 04591af into dotnet:inflight/current Mar 5, 2026
29 checks passed
@github-project-automation github-project-automation bot moved this from Changes Requested to Done in MAUI SDK Ongoing Mar 5, 2026
PureWeen pushed a commit that referenced this pull request Mar 11, 2026
…true (#28983)

### Description of Change

On iOS, the `ActivityIndicator` becomes visible even when `IsVisible =
false` and `IsRunning = true`, effectively ignoring the `IsVisible`
property.

**Root Cause**

Visibility is not being correctly mapped in iOS.

By default, `IsVisible` is `true` for all elements, so we must
explicitly manage visibility based on the `IsRunning` value — especially
since it's expected that the `ActivityIndicator` is hidden by default.

The current implementation seems to work because `IsRunning` defaults to
`false`, which calls `StopAnimating()` and hides the native control.
However, if `HidesWhenStopped` is set to `false`, the control remains
visible without animating — which is incorrect.

To fix this, we explicitly update the visibility inside the `IsRunning`
mapper, just as it's done on Android.


<table>
  <tr>
<th>Before Fix</th>
<th>After Fix</th>
</tr>
<tr>
<td>


https://github.com/user-attachments/assets/19482315-e5ba-4c4e-af2a-2e883d6eef35


</td>
<td>


https://github.com/user-attachments/assets/9c05750d-d7ef-445c-9c65-64e6e142cc45


</td>
</tr>
</table>

### Issues Fixed


Closes #28968

---------

Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions bot pushed a commit that referenced this pull request Mar 11, 2026
…true (#28983)

### Description of Change

On iOS, the `ActivityIndicator` becomes visible even when `IsVisible =
false` and `IsRunning = true`, effectively ignoring the `IsVisible`
property.

**Root Cause**

Visibility is not being correctly mapped in iOS.

By default, `IsVisible` is `true` for all elements, so we must
explicitly manage visibility based on the `IsRunning` value — especially
since it's expected that the `ActivityIndicator` is hidden by default.

The current implementation seems to work because `IsRunning` defaults to
`false`, which calls `StopAnimating()` and hides the native control.
However, if `HidesWhenStopped` is set to `false`, the control remains
visible without animating — which is incorrect.

To fix this, we explicitly update the visibility inside the `IsRunning`
mapper, just as it's done on Android.


<table>
  <tr>
<th>Before Fix</th>
<th>After Fix</th>
</tr>
<tr>
<td>


https://github.com/user-attachments/assets/19482315-e5ba-4c4e-af2a-2e883d6eef35


</td>
<td>


https://github.com/user-attachments/assets/9c05750d-d7ef-445c-9c65-64e6e142cc45


</td>
</tr>
</table>

### Issues Fixed


Closes #28968

---------

Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@PureWeen PureWeen mentioned this pull request Mar 17, 2026
PureWeen pushed a commit that referenced this pull request Mar 19, 2026
…true (#28983)

### Description of Change

On iOS, the `ActivityIndicator` becomes visible even when `IsVisible =
false` and `IsRunning = true`, effectively ignoring the `IsVisible`
property.

**Root Cause**

Visibility is not being correctly mapped in iOS.

By default, `IsVisible` is `true` for all elements, so we must
explicitly manage visibility based on the `IsRunning` value — especially
since it's expected that the `ActivityIndicator` is hidden by default.

The current implementation seems to work because `IsRunning` defaults to
`false`, which calls `StopAnimating()` and hides the native control.
However, if `HidesWhenStopped` is set to `false`, the control remains
visible without animating — which is incorrect.

To fix this, we explicitly update the visibility inside the `IsRunning`
mapper, just as it's done on Android.


<table>
  <tr>
<th>Before Fix</th>
<th>After Fix</th>
</tr>
<tr>
<td>


https://github.com/user-attachments/assets/19482315-e5ba-4c4e-af2a-2e883d6eef35


</td>
<td>


https://github.com/user-attachments/assets/9c05750d-d7ef-445c-9c65-64e6e142cc45


</td>
</tr>
</table>

### Issues Fixed


Closes #28968

---------

Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jfversluis pushed a commit that referenced this pull request Mar 20, 2026
### Root Cause of the issue



- The failing test: `SetVisibility(Visibility.Collapsed)` device test on
iOS.

  Why it fails: PR #28983's fix maps Visibility → MapIsRunning in
  ActivityIndicatorHandler, which bypasses the standard
ViewExtensions.UpdateVisibility path. The standard path calls Collapse()
to
add a CollapseConstraint (an NSLayoutConstraint that zeros the view's
size).
The PR's UpdateIsRunning only sets Hidden = true — it never calls
Collapse()
- Crash in the FeatureMatrix Navigation Page Scenario in the iOS 26
PR #34326 added an else block in UpdateBarTextColor() that explicitly
sets BackButtonAppearance = null, BackIndicatorImage = null, and
BackIndicatorTransitionMaskImage = null on the navigation bar when no
custom color is applied. On iOS versions before 26, assigning null to
these properties was treated as "use system defaults." On iOS 26, the
Liquid Glass rendering pipeline reads these properties during push/pop
navigation transitions and throws an exception when it encounters an
explicit null — it expects either an unset property or a valid object.
Since useCustomColor is false by default (no IconColor set), this
crashes on every standard page navigation.
- Setting ThumbTintList = null in the else block removes the tint
entirely, causing the thumb to appear white instead of the default blue,
because SwitchCompat does not re-resolve its theme colors once the tint
list is cleared.
- SetAdjustViewBounds(false) was being applied to all images regardless
of their Aspect value. When this property is false, Android’s ImageView
does not resize itself based on the image’s intrinsic aspect ratio and
instead expands to fill the available space. As a result, an Image
control with the default AspectFit setting ignored its height constraint
and overflowed its container, causing the image to appear taller than
expected in the screenshot test.(LoadAndVerifyGif, ThemeRelated feature
tests)
- PR #29144 changed the group-detection guard in ObservableGroupedSource
(iOS and Android) from is IEnumerable to is ICollection to prevent
strings (which implement IEnumerable<char>) from being treated as
groups.
While the intent was correct, the change was too broad. Custom group
types that implement only IEnumerable<T> were also excluded. As a
result, _groupCount became zero on iOS and _groups remained empty on
Android, causing grouped CollectionView rendering failures and
IndexOutOfRangeException during Add/Remove operations.
- StepperHandler.iOS.cs compiles for both iOS and Mac Catalyst. On Mac
Catalyst / macOS 26, OperatingSystem.IsIOS() and IsIOSVersionAtLeast(26)
both return true, and the screen is always landscape. As a result, the
20pt glass pill compensation was incorrectly applied, inflating
GetDesiredSize(1,1) to width = 21. (Native View Bounding Box is not
empty - device Test failures)
- In PR #33428, the WindowInsetsCompat.Builder block in
MauiWindowInsetListener.ApplyDefaultWindowInsets was simplified to
return insets; to standardize inset handling. This change was unrelated
to the actual fix for #33344, which only required passing the bottom
inset through as unconsumed.
As part of that refactor, top inset consumption was also removed,
changing the prior contract where the top inset was consumed when
appBarHasContent = true. While normal safe-area scenarios worked
correctly, transient layout states (e.g., temporary Height = 0 during
keyboard dismissal, rotation, animation, or dynamic item generation)
triggered a second inset dispatch. In those moments, the top inset
satisfied the overlap condition and was applied to content before
SafeAreaExtensions could normalize it, causing test failures. Bottom
insets did not regress because their overlap condition cannot be met in
the same transient state. (EntryScrollTest,
HorizontalStackLayout_Spacing_WithLandscape,
VerticalStackLayout_Spacing_WithLandscape and so on failures)

### Description of Change



- Handles the three Visibility cases the same way as
ViewExtensions.UpdateVisibility:

`Visible`: Calls Inflate() (restores layout size) and sets Hidden =
false — identical to UpdateVisibility. Additionally starts/stops the
animation based on IsRunning.
`Hidden`: Calls Inflate() (preserves layout space) and sets Hidden =
true — identical to UpdateVisibility. The indicator keeps its layout
footprint but is invisible.
`Collapsed`: Sets Hidden = true and calls Collapse() (zeros out layout
size via constraints) — identical to UpdateVisibility. The indicator is
both invisible and takes up no space.
- Removed the else block entirely. When no custom color is applied,
these properties should remain untouched. The system defaults work
correctly on their own — there is no need to explicitly reset them to
null
- Removed the else block from UpdateThumbColor in SwitchExtensions.cs.
The default thumb color is managed by SwitchCompat internally from the
Material theme, so no explicit reset is needed.
- Restored the correct logic in ImageViewExtensions.UpdateAspect to call
SetAdjustViewBounds based on the image’s Aspect value:
- The guard has been updated from is ICollection to is IEnumerable &&
not string in the ObservableGroupedSource implementations for both iOS
and Android (GroupsCount(), UpdateGroupTracking(), Add(), Remove()).
This change specifically excludes string while allowing legitimate
custom group types that implement only IEnumerable<T>. The fix restores
the behavior for Issue22320 while keeping all Issue29141 scenarios
working correctly.
-Added !OperatingSystem.IsMacCatalyst() to the guard condition in
GetDesiredSize, restricting the 20pt compensation to real iOS 26+ only —
as intended in the original PR comment.
- Restored the original behavior by consuming the top inset when
appBarHasContent = true, while continuing to pass the bottom inset
through unconsumed (the only change required for #33344). This retains
the Android edge-to-edge fix and restores deterministic safe-area
handling.

### Testing related description of change
EditorNoOverlapAfterRotateToLandscape,
EditorNoOverlapAfterRotateToPortrait,
EntryFocusedShouldNotCauseGapAfterRotation Added cropLeft to remove the
navbar on Android and re-saved the image due to entry text changes in
this commit –
8d17a6d,
91047fb.

DrawStringShouldDrawText – The automation ID set to GraphicsView was not
found by Appium on the Windows platform, so a test condition was added
for Windows to take the image directly instead of waiting for the
GraphicsView.

Added the base images for iOS 26 and Mac that were not added previously.

Re-saved the images that failed due to the wrong iOS version image being
added in the PR.

Re-saved the test images that failed due to this fix PR:
#31254 — e.g.,
GraphicsViewFeatureTests and others.
 
Resaved the slider-related test images due to this fix PR —
#34064.

### Issues Fixed




Fixes #34437 



### Tested the behaviour in the following platforms



- [x] iOS
- [x] Mac

---------

Co-authored-by: SyedAbdulAzeem <syedabdulazeem.a@syncfusion.com>
Co-authored-by: Vignesh-SF3580 <102575140+Vignesh-SF3580@users.noreply.github.com>
Co-authored-by: TamilarasanSF4853 <tamilarasan.velu@syncfusion.com>
Co-authored-by: LogishaSelvarajSF4525 <logisha.selvaraj@syncfusion.com>
github-actions bot pushed a commit that referenced this pull request Mar 20, 2026
…true (#28983)

### Description of Change

On iOS, the `ActivityIndicator` becomes visible even when `IsVisible =
false` and `IsRunning = true`, effectively ignoring the `IsVisible`
property.

**Root Cause**

Visibility is not being correctly mapped in iOS.

By default, `IsVisible` is `true` for all elements, so we must
explicitly manage visibility based on the `IsRunning` value — especially
since it's expected that the `ActivityIndicator` is hidden by default.

The current implementation seems to work because `IsRunning` defaults to
`false`, which calls `StopAnimating()` and hides the native control.
However, if `HidesWhenStopped` is set to `false`, the control remains
visible without animating — which is incorrect.

To fix this, we explicitly update the visibility inside the `IsRunning`
mapper, just as it's done on Android.


<table>
  <tr>
<th>Before Fix</th>
<th>After Fix</th>
</tr>
<tr>
<td>


https://github.com/user-attachments/assets/19482315-e5ba-4c4e-af2a-2e883d6eef35


</td>
<td>


https://github.com/user-attachments/assets/9c05750d-d7ef-445c-9c65-64e6e142cc45


</td>
</tr>
</table>

### Issues Fixed


Closes #28968

---------

Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions bot pushed a commit that referenced this pull request Mar 20, 2026
### Root Cause of the issue



- The failing test: `SetVisibility(Visibility.Collapsed)` device test on
iOS.

  Why it fails: PR #28983's fix maps Visibility → MapIsRunning in
  ActivityIndicatorHandler, which bypasses the standard
ViewExtensions.UpdateVisibility path. The standard path calls Collapse()
to
add a CollapseConstraint (an NSLayoutConstraint that zeros the view's
size).
The PR's UpdateIsRunning only sets Hidden = true — it never calls
Collapse()
- Crash in the FeatureMatrix Navigation Page Scenario in the iOS 26
PR #34326 added an else block in UpdateBarTextColor() that explicitly
sets BackButtonAppearance = null, BackIndicatorImage = null, and
BackIndicatorTransitionMaskImage = null on the navigation bar when no
custom color is applied. On iOS versions before 26, assigning null to
these properties was treated as "use system defaults." On iOS 26, the
Liquid Glass rendering pipeline reads these properties during push/pop
navigation transitions and throws an exception when it encounters an
explicit null — it expects either an unset property or a valid object.
Since useCustomColor is false by default (no IconColor set), this
crashes on every standard page navigation.
- Setting ThumbTintList = null in the else block removes the tint
entirely, causing the thumb to appear white instead of the default blue,
because SwitchCompat does not re-resolve its theme colors once the tint
list is cleared.
- SetAdjustViewBounds(false) was being applied to all images regardless
of their Aspect value. When this property is false, Android’s ImageView
does not resize itself based on the image’s intrinsic aspect ratio and
instead expands to fill the available space. As a result, an Image
control with the default AspectFit setting ignored its height constraint
and overflowed its container, causing the image to appear taller than
expected in the screenshot test.(LoadAndVerifyGif, ThemeRelated feature
tests)
- PR #29144 changed the group-detection guard in ObservableGroupedSource
(iOS and Android) from is IEnumerable to is ICollection to prevent
strings (which implement IEnumerable<char>) from being treated as
groups.
While the intent was correct, the change was too broad. Custom group
types that implement only IEnumerable<T> were also excluded. As a
result, _groupCount became zero on iOS and _groups remained empty on
Android, causing grouped CollectionView rendering failures and
IndexOutOfRangeException during Add/Remove operations.
- StepperHandler.iOS.cs compiles for both iOS and Mac Catalyst. On Mac
Catalyst / macOS 26, OperatingSystem.IsIOS() and IsIOSVersionAtLeast(26)
both return true, and the screen is always landscape. As a result, the
20pt glass pill compensation was incorrectly applied, inflating
GetDesiredSize(1,1) to width = 21. (Native View Bounding Box is not
empty - device Test failures)
- In PR #33428, the WindowInsetsCompat.Builder block in
MauiWindowInsetListener.ApplyDefaultWindowInsets was simplified to
return insets; to standardize inset handling. This change was unrelated
to the actual fix for #33344, which only required passing the bottom
inset through as unconsumed.
As part of that refactor, top inset consumption was also removed,
changing the prior contract where the top inset was consumed when
appBarHasContent = true. While normal safe-area scenarios worked
correctly, transient layout states (e.g., temporary Height = 0 during
keyboard dismissal, rotation, animation, or dynamic item generation)
triggered a second inset dispatch. In those moments, the top inset
satisfied the overlap condition and was applied to content before
SafeAreaExtensions could normalize it, causing test failures. Bottom
insets did not regress because their overlap condition cannot be met in
the same transient state. (EntryScrollTest,
HorizontalStackLayout_Spacing_WithLandscape,
VerticalStackLayout_Spacing_WithLandscape and so on failures)

### Description of Change



- Handles the three Visibility cases the same way as
ViewExtensions.UpdateVisibility:

`Visible`: Calls Inflate() (restores layout size) and sets Hidden =
false — identical to UpdateVisibility. Additionally starts/stops the
animation based on IsRunning.
`Hidden`: Calls Inflate() (preserves layout space) and sets Hidden =
true — identical to UpdateVisibility. The indicator keeps its layout
footprint but is invisible.
`Collapsed`: Sets Hidden = true and calls Collapse() (zeros out layout
size via constraints) — identical to UpdateVisibility. The indicator is
both invisible and takes up no space.
- Removed the else block entirely. When no custom color is applied,
these properties should remain untouched. The system defaults work
correctly on their own — there is no need to explicitly reset them to
null
- Removed the else block from UpdateThumbColor in SwitchExtensions.cs.
The default thumb color is managed by SwitchCompat internally from the
Material theme, so no explicit reset is needed.
- Restored the correct logic in ImageViewExtensions.UpdateAspect to call
SetAdjustViewBounds based on the image’s Aspect value:
- The guard has been updated from is ICollection to is IEnumerable &&
not string in the ObservableGroupedSource implementations for both iOS
and Android (GroupsCount(), UpdateGroupTracking(), Add(), Remove()).
This change specifically excludes string while allowing legitimate
custom group types that implement only IEnumerable<T>. The fix restores
the behavior for Issue22320 while keeping all Issue29141 scenarios
working correctly.
-Added !OperatingSystem.IsMacCatalyst() to the guard condition in
GetDesiredSize, restricting the 20pt compensation to real iOS 26+ only —
as intended in the original PR comment.
- Restored the original behavior by consuming the top inset when
appBarHasContent = true, while continuing to pass the bottom inset
through unconsumed (the only change required for #33344). This retains
the Android edge-to-edge fix and restores deterministic safe-area
handling.

### Testing related description of change
EditorNoOverlapAfterRotateToLandscape,
EditorNoOverlapAfterRotateToPortrait,
EntryFocusedShouldNotCauseGapAfterRotation Added cropLeft to remove the
navbar on Android and re-saved the image due to entry text changes in
this commit –
8d17a6d,
91047fb.

DrawStringShouldDrawText – The automation ID set to GraphicsView was not
found by Appium on the Windows platform, so a test condition was added
for Windows to take the image directly instead of waiting for the
GraphicsView.

Added the base images for iOS 26 and Mac that were not added previously.

Re-saved the images that failed due to the wrong iOS version image being
added in the PR.

Re-saved the test images that failed due to this fix PR:
#31254 — e.g.,
GraphicsViewFeatureTests and others.
 
Resaved the slider-related test images due to this fix PR —
#34064.

### Issues Fixed




Fixes #34437 



### Tested the behaviour in the following platforms



- [x] iOS
- [x] Mac

---------

Co-authored-by: SyedAbdulAzeem <syedabdulazeem.a@syncfusion.com>
Co-authored-by: Vignesh-SF3580 <102575140+Vignesh-SF3580@users.noreply.github.com>
Co-authored-by: TamilarasanSF4853 <tamilarasan.velu@syncfusion.com>
Co-authored-by: LogishaSelvarajSF4525 <logisha.selvaraj@syncfusion.com>
github-actions bot pushed a commit that referenced this pull request Mar 22, 2026
…true (#28983)

### Description of Change

On iOS, the `ActivityIndicator` becomes visible even when `IsVisible =
false` and `IsRunning = true`, effectively ignoring the `IsVisible`
property.

**Root Cause**

Visibility is not being correctly mapped in iOS.

By default, `IsVisible` is `true` for all elements, so we must
explicitly manage visibility based on the `IsRunning` value — especially
since it's expected that the `ActivityIndicator` is hidden by default.

The current implementation seems to work because `IsRunning` defaults to
`false`, which calls `StopAnimating()` and hides the native control.
However, if `HidesWhenStopped` is set to `false`, the control remains
visible without animating — which is incorrect.

To fix this, we explicitly update the visibility inside the `IsRunning`
mapper, just as it's done on Android.


<table>
  <tr>
<th>Before Fix</th>
<th>After Fix</th>
</tr>
<tr>
<td>


https://github.com/user-attachments/assets/19482315-e5ba-4c4e-af2a-2e883d6eef35


</td>
<td>


https://github.com/user-attachments/assets/9c05750d-d7ef-445c-9c65-64e6e142cc45


</td>
</tr>
</table>

### Issues Fixed


Closes #28968

---------

Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions bot pushed a commit that referenced this pull request Mar 22, 2026
### Root Cause of the issue



- The failing test: `SetVisibility(Visibility.Collapsed)` device test on
iOS.

  Why it fails: PR #28983's fix maps Visibility → MapIsRunning in
  ActivityIndicatorHandler, which bypasses the standard
ViewExtensions.UpdateVisibility path. The standard path calls Collapse()
to
add a CollapseConstraint (an NSLayoutConstraint that zeros the view's
size).
The PR's UpdateIsRunning only sets Hidden = true — it never calls
Collapse()
- Crash in the FeatureMatrix Navigation Page Scenario in the iOS 26
PR #34326 added an else block in UpdateBarTextColor() that explicitly
sets BackButtonAppearance = null, BackIndicatorImage = null, and
BackIndicatorTransitionMaskImage = null on the navigation bar when no
custom color is applied. On iOS versions before 26, assigning null to
these properties was treated as "use system defaults." On iOS 26, the
Liquid Glass rendering pipeline reads these properties during push/pop
navigation transitions and throws an exception when it encounters an
explicit null — it expects either an unset property or a valid object.
Since useCustomColor is false by default (no IconColor set), this
crashes on every standard page navigation.
- Setting ThumbTintList = null in the else block removes the tint
entirely, causing the thumb to appear white instead of the default blue,
because SwitchCompat does not re-resolve its theme colors once the tint
list is cleared.
- SetAdjustViewBounds(false) was being applied to all images regardless
of their Aspect value. When this property is false, Android’s ImageView
does not resize itself based on the image’s intrinsic aspect ratio and
instead expands to fill the available space. As a result, an Image
control with the default AspectFit setting ignored its height constraint
and overflowed its container, causing the image to appear taller than
expected in the screenshot test.(LoadAndVerifyGif, ThemeRelated feature
tests)
- PR #29144 changed the group-detection guard in ObservableGroupedSource
(iOS and Android) from is IEnumerable to is ICollection to prevent
strings (which implement IEnumerable<char>) from being treated as
groups.
While the intent was correct, the change was too broad. Custom group
types that implement only IEnumerable<T> were also excluded. As a
result, _groupCount became zero on iOS and _groups remained empty on
Android, causing grouped CollectionView rendering failures and
IndexOutOfRangeException during Add/Remove operations.
- StepperHandler.iOS.cs compiles for both iOS and Mac Catalyst. On Mac
Catalyst / macOS 26, OperatingSystem.IsIOS() and IsIOSVersionAtLeast(26)
both return true, and the screen is always landscape. As a result, the
20pt glass pill compensation was incorrectly applied, inflating
GetDesiredSize(1,1) to width = 21. (Native View Bounding Box is not
empty - device Test failures)
- In PR #33428, the WindowInsetsCompat.Builder block in
MauiWindowInsetListener.ApplyDefaultWindowInsets was simplified to
return insets; to standardize inset handling. This change was unrelated
to the actual fix for #33344, which only required passing the bottom
inset through as unconsumed.
As part of that refactor, top inset consumption was also removed,
changing the prior contract where the top inset was consumed when
appBarHasContent = true. While normal safe-area scenarios worked
correctly, transient layout states (e.g., temporary Height = 0 during
keyboard dismissal, rotation, animation, or dynamic item generation)
triggered a second inset dispatch. In those moments, the top inset
satisfied the overlap condition and was applied to content before
SafeAreaExtensions could normalize it, causing test failures. Bottom
insets did not regress because their overlap condition cannot be met in
the same transient state. (EntryScrollTest,
HorizontalStackLayout_Spacing_WithLandscape,
VerticalStackLayout_Spacing_WithLandscape and so on failures)

### Description of Change



- Handles the three Visibility cases the same way as
ViewExtensions.UpdateVisibility:

`Visible`: Calls Inflate() (restores layout size) and sets Hidden =
false — identical to UpdateVisibility. Additionally starts/stops the
animation based on IsRunning.
`Hidden`: Calls Inflate() (preserves layout space) and sets Hidden =
true — identical to UpdateVisibility. The indicator keeps its layout
footprint but is invisible.
`Collapsed`: Sets Hidden = true and calls Collapse() (zeros out layout
size via constraints) — identical to UpdateVisibility. The indicator is
both invisible and takes up no space.
- Removed the else block entirely. When no custom color is applied,
these properties should remain untouched. The system defaults work
correctly on their own — there is no need to explicitly reset them to
null
- Removed the else block from UpdateThumbColor in SwitchExtensions.cs.
The default thumb color is managed by SwitchCompat internally from the
Material theme, so no explicit reset is needed.
- Restored the correct logic in ImageViewExtensions.UpdateAspect to call
SetAdjustViewBounds based on the image’s Aspect value:
- The guard has been updated from is ICollection to is IEnumerable &&
not string in the ObservableGroupedSource implementations for both iOS
and Android (GroupsCount(), UpdateGroupTracking(), Add(), Remove()).
This change specifically excludes string while allowing legitimate
custom group types that implement only IEnumerable<T>. The fix restores
the behavior for Issue22320 while keeping all Issue29141 scenarios
working correctly.
-Added !OperatingSystem.IsMacCatalyst() to the guard condition in
GetDesiredSize, restricting the 20pt compensation to real iOS 26+ only —
as intended in the original PR comment.
- Restored the original behavior by consuming the top inset when
appBarHasContent = true, while continuing to pass the bottom inset
through unconsumed (the only change required for #33344). This retains
the Android edge-to-edge fix and restores deterministic safe-area
handling.

### Testing related description of change
EditorNoOverlapAfterRotateToLandscape,
EditorNoOverlapAfterRotateToPortrait,
EntryFocusedShouldNotCauseGapAfterRotation Added cropLeft to remove the
navbar on Android and re-saved the image due to entry text changes in
this commit –
8d17a6d,
91047fb.

DrawStringShouldDrawText – The automation ID set to GraphicsView was not
found by Appium on the Windows platform, so a test condition was added
for Windows to take the image directly instead of waiting for the
GraphicsView.

Added the base images for iOS 26 and Mac that were not added previously.

Re-saved the images that failed due to the wrong iOS version image being
added in the PR.

Re-saved the test images that failed due to this fix PR:
#31254 — e.g.,
GraphicsViewFeatureTests and others.
 
Resaved the slider-related test images due to this fix PR —
#34064.

### Issues Fixed




Fixes #34437 



### Tested the behaviour in the following platforms



- [x] iOS
- [x] Mac

---------

Co-authored-by: SyedAbdulAzeem <syedabdulazeem.a@syncfusion.com>
Co-authored-by: Vignesh-SF3580 <102575140+Vignesh-SF3580@users.noreply.github.com>
Co-authored-by: TamilarasanSF4853 <tamilarasan.velu@syncfusion.com>
Co-authored-by: LogishaSelvarajSF4525 <logisha.selvaraj@syncfusion.com>
KarthikRajaKalaimani pushed a commit to KarthikRajaKalaimani/maui that referenced this pull request Mar 23, 2026
- The failing test: `SetVisibility(Visibility.Collapsed)` device test on
iOS.

  Why it fails: PR dotnet#28983's fix maps Visibility → MapIsRunning in
  ActivityIndicatorHandler, which bypasses the standard
ViewExtensions.UpdateVisibility path. The standard path calls Collapse()
to
add a CollapseConstraint (an NSLayoutConstraint that zeros the view's
size).
The PR's UpdateIsRunning only sets Hidden = true — it never calls
Collapse()
- Crash in the FeatureMatrix Navigation Page Scenario in the iOS 26
PR dotnet#34326 added an else block in UpdateBarTextColor() that explicitly
sets BackButtonAppearance = null, BackIndicatorImage = null, and
BackIndicatorTransitionMaskImage = null on the navigation bar when no
custom color is applied. On iOS versions before 26, assigning null to
these properties was treated as "use system defaults." On iOS 26, the
Liquid Glass rendering pipeline reads these properties during push/pop
navigation transitions and throws an exception when it encounters an
explicit null — it expects either an unset property or a valid object.
Since useCustomColor is false by default (no IconColor set), this
crashes on every standard page navigation.
- Setting ThumbTintList = null in the else block removes the tint
entirely, causing the thumb to appear white instead of the default blue,
because SwitchCompat does not re-resolve its theme colors once the tint
list is cleared.
- SetAdjustViewBounds(false) was being applied to all images regardless
of their Aspect value. When this property is false, Android’s ImageView
does not resize itself based on the image’s intrinsic aspect ratio and
instead expands to fill the available space. As a result, an Image
control with the default AspectFit setting ignored its height constraint
and overflowed its container, causing the image to appear taller than
expected in the screenshot test.(LoadAndVerifyGif, ThemeRelated feature
tests)
- PR dotnet#29144 changed the group-detection guard in ObservableGroupedSource
(iOS and Android) from is IEnumerable to is ICollection to prevent
strings (which implement IEnumerable<char>) from being treated as
groups.
While the intent was correct, the change was too broad. Custom group
types that implement only IEnumerable<T> were also excluded. As a
result, _groupCount became zero on iOS and _groups remained empty on
Android, causing grouped CollectionView rendering failures and
IndexOutOfRangeException during Add/Remove operations.
- StepperHandler.iOS.cs compiles for both iOS and Mac Catalyst. On Mac
Catalyst / macOS 26, OperatingSystem.IsIOS() and IsIOSVersionAtLeast(26)
both return true, and the screen is always landscape. As a result, the
20pt glass pill compensation was incorrectly applied, inflating
GetDesiredSize(1,1) to width = 21. (Native View Bounding Box is not
empty - device Test failures)
- In PR dotnet#33428, the WindowInsetsCompat.Builder block in
MauiWindowInsetListener.ApplyDefaultWindowInsets was simplified to
return insets; to standardize inset handling. This change was unrelated
to the actual fix for dotnet#33344, which only required passing the bottom
inset through as unconsumed.
As part of that refactor, top inset consumption was also removed,
changing the prior contract where the top inset was consumed when
appBarHasContent = true. While normal safe-area scenarios worked
correctly, transient layout states (e.g., temporary Height = 0 during
keyboard dismissal, rotation, animation, or dynamic item generation)
triggered a second inset dispatch. In those moments, the top inset
satisfied the overlap condition and was applied to content before
SafeAreaExtensions could normalize it, causing test failures. Bottom
insets did not regress because their overlap condition cannot be met in
the same transient state. (EntryScrollTest,
HorizontalStackLayout_Spacing_WithLandscape,
VerticalStackLayout_Spacing_WithLandscape and so on failures)

- Handles the three Visibility cases the same way as
ViewExtensions.UpdateVisibility:

`Visible`: Calls Inflate() (restores layout size) and sets Hidden =
false — identical to UpdateVisibility. Additionally starts/stops the
animation based on IsRunning.
`Hidden`: Calls Inflate() (preserves layout space) and sets Hidden =
true — identical to UpdateVisibility. The indicator keeps its layout
footprint but is invisible.
`Collapsed`: Sets Hidden = true and calls Collapse() (zeros out layout
size via constraints) — identical to UpdateVisibility. The indicator is
both invisible and takes up no space.
- Removed the else block entirely. When no custom color is applied,
these properties should remain untouched. The system defaults work
correctly on their own — there is no need to explicitly reset them to
null
- Removed the else block from UpdateThumbColor in SwitchExtensions.cs.
The default thumb color is managed by SwitchCompat internally from the
Material theme, so no explicit reset is needed.
- Restored the correct logic in ImageViewExtensions.UpdateAspect to call
SetAdjustViewBounds based on the image’s Aspect value:
- The guard has been updated from is ICollection to is IEnumerable &&
not string in the ObservableGroupedSource implementations for both iOS
and Android (GroupsCount(), UpdateGroupTracking(), Add(), Remove()).
This change specifically excludes string while allowing legitimate
custom group types that implement only IEnumerable<T>. The fix restores
the behavior for Issue22320 while keeping all Issue29141 scenarios
working correctly.
-Added !OperatingSystem.IsMacCatalyst() to the guard condition in
GetDesiredSize, restricting the 20pt compensation to real iOS 26+ only —
as intended in the original PR comment.
- Restored the original behavior by consuming the top inset when
appBarHasContent = true, while continuing to pass the bottom inset
through unconsumed (the only change required for dotnet#33344). This retains
the Android edge-to-edge fix and restores deterministic safe-area
handling.

EditorNoOverlapAfterRotateToLandscape,
EditorNoOverlapAfterRotateToPortrait,
EntryFocusedShouldNotCauseGapAfterRotation Added cropLeft to remove the
navbar on Android and re-saved the image due to entry text changes in
this commit –
dotnet@8d17a6d,
dotnet@91047fb.

DrawStringShouldDrawText – The automation ID set to GraphicsView was not
found by Appium on the Windows platform, so a test condition was added
for Windows to take the image directly instead of waiting for the
GraphicsView.

Added the base images for iOS 26 and Mac that were not added previously.

Re-saved the images that failed due to the wrong iOS version image being
added in the PR.

Re-saved the test images that failed due to this fix PR:
dotnet#31254 — e.g.,
GraphicsViewFeatureTests and others.

Resaved the slider-related test images due to this fix PR —
dotnet#34064.

Fixes dotnet#34437

- [x] iOS
- [x] Mac

---------

Co-authored-by: SyedAbdulAzeem <syedabdulazeem.a@syncfusion.com>
Co-authored-by: Vignesh-SF3580 <102575140+Vignesh-SF3580@users.noreply.github.com>
Co-authored-by: TamilarasanSF4853 <tamilarasan.velu@syncfusion.com>
Co-authored-by: LogishaSelvarajSF4525 <logisha.selvaraj@syncfusion.com>
@kubaflo kubaflo removed the s/agent-fix-win AI found a better alternative fix than the PR label Mar 23, 2026
KarthikRajaKalaimani pushed a commit to KarthikRajaKalaimani/maui that referenced this pull request Mar 24, 2026
- The failing test: `SetVisibility(Visibility.Collapsed)` device test on
iOS.

  Why it fails: PR dotnet#28983's fix maps Visibility → MapIsRunning in
  ActivityIndicatorHandler, which bypasses the standard
ViewExtensions.UpdateVisibility path. The standard path calls Collapse()
to
add a CollapseConstraint (an NSLayoutConstraint that zeros the view's
size).
The PR's UpdateIsRunning only sets Hidden = true — it never calls
Collapse()
- Crash in the FeatureMatrix Navigation Page Scenario in the iOS 26
PR dotnet#34326 added an else block in UpdateBarTextColor() that explicitly
sets BackButtonAppearance = null, BackIndicatorImage = null, and
BackIndicatorTransitionMaskImage = null on the navigation bar when no
custom color is applied. On iOS versions before 26, assigning null to
these properties was treated as "use system defaults." On iOS 26, the
Liquid Glass rendering pipeline reads these properties during push/pop
navigation transitions and throws an exception when it encounters an
explicit null — it expects either an unset property or a valid object.
Since useCustomColor is false by default (no IconColor set), this
crashes on every standard page navigation.
- Setting ThumbTintList = null in the else block removes the tint
entirely, causing the thumb to appear white instead of the default blue,
because SwitchCompat does not re-resolve its theme colors once the tint
list is cleared.
- SetAdjustViewBounds(false) was being applied to all images regardless
of their Aspect value. When this property is false, Android’s ImageView
does not resize itself based on the image’s intrinsic aspect ratio and
instead expands to fill the available space. As a result, an Image
control with the default AspectFit setting ignored its height constraint
and overflowed its container, causing the image to appear taller than
expected in the screenshot test.(LoadAndVerifyGif, ThemeRelated feature
tests)
- PR dotnet#29144 changed the group-detection guard in ObservableGroupedSource
(iOS and Android) from is IEnumerable to is ICollection to prevent
strings (which implement IEnumerable<char>) from being treated as
groups.
While the intent was correct, the change was too broad. Custom group
types that implement only IEnumerable<T> were also excluded. As a
result, _groupCount became zero on iOS and _groups remained empty on
Android, causing grouped CollectionView rendering failures and
IndexOutOfRangeException during Add/Remove operations.
- StepperHandler.iOS.cs compiles for both iOS and Mac Catalyst. On Mac
Catalyst / macOS 26, OperatingSystem.IsIOS() and IsIOSVersionAtLeast(26)
both return true, and the screen is always landscape. As a result, the
20pt glass pill compensation was incorrectly applied, inflating
GetDesiredSize(1,1) to width = 21. (Native View Bounding Box is not
empty - device Test failures)
- In PR dotnet#33428, the WindowInsetsCompat.Builder block in
MauiWindowInsetListener.ApplyDefaultWindowInsets was simplified to
return insets; to standardize inset handling. This change was unrelated
to the actual fix for dotnet#33344, which only required passing the bottom
inset through as unconsumed.
As part of that refactor, top inset consumption was also removed,
changing the prior contract where the top inset was consumed when
appBarHasContent = true. While normal safe-area scenarios worked
correctly, transient layout states (e.g., temporary Height = 0 during
keyboard dismissal, rotation, animation, or dynamic item generation)
triggered a second inset dispatch. In those moments, the top inset
satisfied the overlap condition and was applied to content before
SafeAreaExtensions could normalize it, causing test failures. Bottom
insets did not regress because their overlap condition cannot be met in
the same transient state. (EntryScrollTest,
HorizontalStackLayout_Spacing_WithLandscape,
VerticalStackLayout_Spacing_WithLandscape and so on failures)

- Handles the three Visibility cases the same way as
ViewExtensions.UpdateVisibility:

`Visible`: Calls Inflate() (restores layout size) and sets Hidden =
false — identical to UpdateVisibility. Additionally starts/stops the
animation based on IsRunning.
`Hidden`: Calls Inflate() (preserves layout space) and sets Hidden =
true — identical to UpdateVisibility. The indicator keeps its layout
footprint but is invisible.
`Collapsed`: Sets Hidden = true and calls Collapse() (zeros out layout
size via constraints) — identical to UpdateVisibility. The indicator is
both invisible and takes up no space.
- Removed the else block entirely. When no custom color is applied,
these properties should remain untouched. The system defaults work
correctly on their own — there is no need to explicitly reset them to
null
- Removed the else block from UpdateThumbColor in SwitchExtensions.cs.
The default thumb color is managed by SwitchCompat internally from the
Material theme, so no explicit reset is needed.
- Restored the correct logic in ImageViewExtensions.UpdateAspect to call
SetAdjustViewBounds based on the image’s Aspect value:
- The guard has been updated from is ICollection to is IEnumerable &&
not string in the ObservableGroupedSource implementations for both iOS
and Android (GroupsCount(), UpdateGroupTracking(), Add(), Remove()).
This change specifically excludes string while allowing legitimate
custom group types that implement only IEnumerable<T>. The fix restores
the behavior for Issue22320 while keeping all Issue29141 scenarios
working correctly.
-Added !OperatingSystem.IsMacCatalyst() to the guard condition in
GetDesiredSize, restricting the 20pt compensation to real iOS 26+ only —
as intended in the original PR comment.
- Restored the original behavior by consuming the top inset when
appBarHasContent = true, while continuing to pass the bottom inset
through unconsumed (the only change required for dotnet#33344). This retains
the Android edge-to-edge fix and restores deterministic safe-area
handling.

EditorNoOverlapAfterRotateToLandscape,
EditorNoOverlapAfterRotateToPortrait,
EntryFocusedShouldNotCauseGapAfterRotation Added cropLeft to remove the
navbar on Android and re-saved the image due to entry text changes in
this commit –
dotnet@8d17a6d,
dotnet@91047fb.

DrawStringShouldDrawText – The automation ID set to GraphicsView was not
found by Appium on the Windows platform, so a test condition was added
for Windows to take the image directly instead of waiting for the
GraphicsView.

Added the base images for iOS 26 and Mac that were not added previously.

Re-saved the images that failed due to the wrong iOS version image being
added in the PR.

Re-saved the test images that failed due to this fix PR:
dotnet#31254 — e.g.,
GraphicsViewFeatureTests and others.

Resaved the slider-related test images due to this fix PR —
dotnet#34064.

Fixes dotnet#34437

- [x] iOS
- [x] Mac

---------

Co-authored-by: SyedAbdulAzeem <syedabdulazeem.a@syncfusion.com>
Co-authored-by: Vignesh-SF3580 <102575140+Vignesh-SF3580@users.noreply.github.com>
Co-authored-by: TamilarasanSF4853 <tamilarasan.velu@syncfusion.com>
Co-authored-by: LogishaSelvarajSF4525 <logisha.selvaraj@syncfusion.com>
PureWeen added a commit that referenced this pull request Mar 24, 2026
## What's Coming

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


## Activityindicator
- [Android] Implemented material3 support for ActivityIndicator by
@Dhivya-SF4094 in #33481
  <details>
  <summary>🔧 Fixes</summary>

- [Implement material3 support for
ActivityIndicator](#33479)
  </details>

- [iOS] Fix: ActivityIndicator IsRunning ignores IsVisible when set to
true by @bhavanesh2001 in #28983
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] [ActivityIndicator] `IsRunning` ignores `IsVisible` when set to
`true`](#28968)
  </details>

## Button
- [iOS] Button RTL text and image overlap - fix by @kubaflo in
#29041

## Checkbox
- [iOS/MacCatalyst] Fix CheckBox foreground color not resetting when set
to null by @Ahamed-Ali in #34284
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] Color of the checkBox control is not properly worked on dynamic
scenarios](#34278)
  </details>

## CollectionView
- [iOS] Fix: CollectionView does not clear selection when SelectedItem
is set to null by @Tamilarasan-Paranthaman in
#30420
  <details>
  <summary>🔧 Fixes</summary>

- [CollectionView not being able to remove selected item highlight on
iOS](#30363)
- [[MAUI] Select items traces are
preserved](#26187)
  </details>

- [iOS] CV2 ItemsLayout update by @kubaflo in
#28675
  <details>
  <summary>🔧 Fixes</summary>

- [CollectionView CollectionViewHandler2 doesnt change ItemsLayout on
DataTrigger](#28656)
- [iOS CollectionView doesn't respect a change to ItemsLayout when using
Items2.CollectionViewHandler2](#31259)
  </details>

- [iOS][CV2] Fix CollectionView renders large empty space at bottom of
view by @devanathan-vaithiyanathan in
#31215
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] [MacCatalyst] CollectionView renders large empty space at
bottom of view](#17799)
- [[iOS/Mac] CollectionView2 EmptyView takes up large horizontal space
even when the content is
small](#33201)
  </details>

- [iOS] Fixed issue where group Header/Footer template was set to all
items when IsGrouped was true for an ObservableCollection by
@Tamilarasan-Paranthaman in #29144
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] Group Header/Footer Repeated for All Items When IsGrouped is
True for ObservableCollection in
CollectionView](#29141)
  </details>

- [Android] Fix CollectionView selection crash with HeaderTemplate by
@NirmalKumarYuvaraj in #34275
  <details>
  <summary>🔧 Fixes</summary>

- [[Bug] [Android] System.ArgumentOutOfRangeException: Index was out of
range. Must be non-negative and less than the size of the collection.
Parameter name: index](#34247)
  </details>

## DateTimePicker
- [iOS] Fix TimePicker AM/PM frequently changes when the app is closed
and reopened by @devanathan-vaithiyanathan in
#31066
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] TimePicker AM/PM frequently changes when the app is closed and
reopened](#30837)
- [Maui 10 iOS TimePicker Strange Characters in place of
AM/PM](#33722)
  </details>

- Android TimePicker ignores 24 hour system setting when using Format
Property - fix by @kubaflo in #28797
  <details>
  <summary>🔧 Fixes</summary>

- [Android TimePicker ignores 24 hour system setting when using Format
Property](#28784)
  </details>

## Drawing
- [iOS, Mac, Windows] GraphicsView: Fix Background/BackgroundColor not
updating by @NirmalKumarYuvaraj in
#31254
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS, Mac, Windows] GraphicsView does not change the
Background/BackgroundColor](#31239)
  </details>

- [iOS] GraphicsView DrawString - fix by @kubaflo in
#26304
  <details>
  <summary>🔧 Fixes</summary>

- [DrawString not rendering in
iOS.](#24450)
- [GraphicsView DrawString not rendering in
iOS](#8486)
- [DrawString doesn't work on
maccatalyst](#4993)
  </details>

- [Android] - Fix Shadow Rendering For Transparent Fill, Stroke (Lines),
and Text on Shapes by @prakashKannanSf3972 in
#29528
  <details>
  <summary>🔧 Fixes</summary>

- [Ellipse Transparency Not Rendered When Drawing Arc Inside the Ellipse
Using GraphicsView on
Android](#29394)
  </details>

- Revert "[iOS, Mac, Windows] GraphicsView: Fix
Background/BackgroundColor not updating (#31254)" by @Ahamed-Ali via
@Copilot in #34508

## Entry
- [iOS 26] Fix Entry MaxLength not enforced due to new multi-range
delegate by @kubaflo in #32045
  <details>
  <summary>🔧 Fixes</summary>

- [iOS 26 - The MaxLength property value is not respected on an Entry
control.](#32016)
- [.NET MAUI Entry Maximum Length not working on iOS and
macOS](#33316)
  </details>

- [iOS] Fixed Entry with IsPassword toggling loses previously entered
text by @SubhikshaSf4851 in #30572
  <details>
  <summary>🔧 Fixes</summary>

- [Entry with IsPassword toggling loses previously entered text on iOS
when IsPassword is
re-enabled](#30085)
  </details>

## Essentials
- Fix for FilePicker PickMultipleAsync nullable reference type by
@SuthiYuvaraj in #33163
  <details>
  <summary>🔧 Fixes</summary>

- [FilePicker PickMultipleAsync nullable reference
type](#33114)
  </details>

- Replace deprecated NetworkReachability with NWPathMonitor on iOS/macOS
by @jfversluis via @Copilot in #32354
  <details>
  <summary>🔧 Fixes</summary>

- [NetworkReachability is obsolete on iOS/maccatalyst
17.4+](#32312)
- [Use NWPathMonitor on iOS for Essentials
Connectivity](#2574)
  </details>

## Essentials Connectivity
- Update Android Connectivity implementation to use modern APIs by
@jfversluis via @Copilot in #30348
  <details>
  <summary>🔧 Fixes</summary>

- [Update the Android Connectivity implementation to user modern
APIs](#30347)
  </details>

## Flyout
- [iOS] Fixed Flyout icon not updating when root page changes using
InsertPageBefore by @Vignesh-SF3580 in
#29924
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] Flyout icon not replaced by back button when root page is
changed using
InsertPageBefore](#29921)
  </details>

## Flyoutpage
- [iOS] Flyout Items Not Displayed in RightToLeft FlowDirection in
Landscape - fix by @kubaflo in #26762
  <details>
  <summary>🔧 Fixes</summary>

- [Flyout Items Not Displayed in RightToLeft FlowDirection on iOS in
Landscape Orientation and Hamburger Icon Positioned
Incorrectly](#26726)
  </details>

## Image
- [Android] Implemented Material3 support for Image by @Dhivya-SF4094 in
#33661
  <details>
  <summary>🔧 Fixes</summary>

- [Implement Material3 support for
Image](#33660)
  </details>

## Keyboard
- [iOS] Fix gap at top of view after rotating device while Entry
keyboard is visible by @praveenkumarkarunanithi in
#34328
  <details>
  <summary>🔧 Fixes</summary>

- [Focusing and entering texts on entry control causes a gap at the top
after rotating simulator.](#33407)
  </details>

## Label
- [Android] Support for images inside HTML label by @kubaflo in
#21679
  <details>
  <summary>🔧 Fixes</summary>

- [Label with HTML TextType does not display images on
Android](#21044)
  </details>

- [fix] ContentLabel Moved to a nested class to prevent CS0122 in
external source generators by @SubhikshaSf4851 in
#34514
  <details>
  <summary>🔧 Fixes</summary>

- [[MAUI] Building Maui App with sample content results CS0122
errors.](#34512)
  </details>

## Layout
- Optimize ordering of children in Flex layout by @symbiogenesis in
#21961

- [Android] Fix control size properties not available during Loaded
event by @Vignesh-SF3580 in #31590
  <details>
  <summary>🔧 Fixes</summary>

- [CollectionView on Android does not provide height, width, logical
children once loaded, works fine on
Windows](#14364)
- [Control's Loaded event invokes before calling its measure override
method.](#14160)
  </details>

## Mediapicker
- [iOS/Android] MediaPicker: Fix image orientation when RotateImage=true
by @michalpobuta in #33892
  <details>
  <summary>🔧 Fixes</summary>

- [MediaPicker.PickPhotosAsync does not preserve image
orientation](#32650)
  </details>

## Modal
- [Windows] Fix modal page keyboard focus not shifting to newly opened
modal by @jfversluis in #34212
  <details>
  <summary>🔧 Fixes</summary>

- [Keyboard focus does not shift to a newly opened modal page: Pressing
enter clicks the button on the page beneath the modal
page](#22938)
  </details>

## Navigation
- [iOS26] Apply view margins in title view by @kubaflo in
#32205
  <details>
  <summary>🔧 Fixes</summary>

- [NavigationPage TitleView iOS
26](#32200)
  </details>

- [iOS] System.NullReferenceException at
NavigationRenderer.SetStatusBarStyle() by @kubaflo in
#29564
  <details>
  <summary>🔧 Fixes</summary>

- [System.NullReferenceException at
NavigationRenderer.SetStatusBarStyle()](#29535)
  </details>

- [iOS 26] Fix back button color not applied for NavigationPage by
@Shalini-Ashokan in #34326
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] Color not applied to the Back button text or image on iOS
26](#33966)
  </details>

## Picker
- Fix Picker layout on Mac Catalyst 26+ by @kubaflo in
#33146
  <details>
  <summary>🔧 Fixes</summary>

- [[MacOS 26] Text on picker options are not centered on macOS
26.1](#33229)
  </details>

## Progressbar
- [Android] Implemented Material3 support for ProgressBar by
@SyedAbdulAzeemSF4852 in #33926
  <details>
  <summary>🔧 Fixes</summary>

- [Implement Material3 support for
Progressbar](#33925)
  </details>

## RadioButton
- [iOS, Mac] Fix for RadioButton TextColor for plain Content not working
by @HarishwaranVijayakumar in #31940
  <details>
  <summary>🔧 Fixes</summary>

- [RadioButton: TextColor for plain Content not working on
iOS](#18011)
  </details>

- [All Platforms] Fix RadioButton warning when ControlTemplate is set
with View content by @kubaflo in
#33839
  <details>
  <summary>🔧 Fixes</summary>

- [Seeking clarification on RadioButton + ControlTemplate + Content
documentation](#33829)
  </details>

- Visual state change for disabled RadioButton by @kubaflo in
#23471
  <details>
  <summary>🔧 Fixes</summary>

- [RadioButton disabled UI issue -
iOS](#18668)
  </details>

## SafeArea
- [Android] Fix for TabbedPage BottomNavigation BarBackgroundColor not
extending to system navigation bar by @praveenkumarkarunanithi in
#33428
  <details>
  <summary>🔧 Fixes</summary>

- [[Android] TabbedPage BottomNavigation BarBackgroundColor does not
extend to system navigation bar area in Edge-to-Edge
mode](#33344)
  </details>

## ScrollView
- [Android] ScrollView: Fix HorizontalScrollBarVisibility not updating
immediately at runtime by @SubhikshaSf4851 in
#33528
  <details>
  <summary>🔧 Fixes</summary>

- [Runtime Scrollbar visibility not updating correctly on Android and
macOS platforms.](#33400)
  </details>

- Fixed crash when calling ItemsView.ScrollTo on unloaded CollectionView
by @kubaflo in #25444
  <details>
  <summary>🔧 Fixes</summary>

- [App crashes when calling ItemsView.ScrollTo on unloaded
CollectionView](#23014)
  </details>

## Shell
- [Shell] Update logic for iOS large title display in ShellItemRenderer
by @kubaflo in #33246

- [iOS][Shell] Fix navigation lifecycle and back button for More tab (>5
tabs) by @kubaflo in #27932
  <details>
  <summary>🔧 Fixes</summary>

- [OnAppearing and OnNavigatedTo does not work when using extended
Tabbar (tabbar with more than 5 tabs) on
IOS.](#27799)
- [Shell.BackButtonBehavior does not work when using extended Tabbar
(tabbar with more than 5 tabs)on
IOS.](#27800)
- [Shell TabBar More button causes ViewModel command binding
disconnection on back
navigation](#30862)
- [Content page onappearing not firing if tabs are on the more tab on
IOS](#31166)
  </details>

- [iOS 26] Fix tab bar ghosting when navigating from modal to tabbed
Shell content by @SubhikshaSf4851 in
#34254
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] Tab bar ghosting issue on iOS 26 (liquid
glass)](#34143)
  </details>

- Fix for Shell tab visibility not updating when navigating back
multiple pages by @BagavathiPerumal in
#34403
  <details>
  <summary>🔧 Fixes</summary>

- [Changing Shell Tab Visibility when navigating back multiple pages
ignores Shell Tab
Visibility](#33351)
  </details>

- [iOS/Mac] Fixed OnBackButtonPressed not firing for Shell Navigation
Bar Button by @Dhivya-SF4094 in
#34401
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] OnBackButtonPressed not firing for Shell Navigation Bar
button](#34190)
  </details>

## Slider
- [iOS] Fix for Slider ThumbImageSource is not centered properly on iOS
26 by @HarishwaranVijayakumar in
#34019
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS 26] Slider ThumbImageSource is not centered
properly](#33967)
  </details>

- [Android] Fix improper rendering of ThumbimageSource in Slider by
@NirmalKumarYuvaraj in #34064
  <details>
  <summary>🔧 Fixes</summary>

- [[Slider] MAUI Slider thumb image is big on
android](#13258)
  </details>

## Stepper
- [iOS] Fix Stepper layout overlap in landscape on iOS 26 by
@Vignesh-SF3580 in #34325
  <details>
  <summary>🔧 Fixes</summary>

- [[.NET10] D10 - Customize cursor position - Rotating simulator makes
the button and label
overlap](#34273)
  </details>

## SwipeView
- [iOS] SwipeView: Honor FontImageSource.Color in SwipeItem icon by
@kubaflo in #27389
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] SwipeView: SwipeItem.IconImageSource.FontImageSource color
value not honored](#27377)
  </details>

## Switch
- [Android] Fix Switch thumb shadow missing when ThumbColor is set by
@Shalini-Ashokan in #33960
  <details>
  <summary>🔧 Fixes</summary>

- [Android Switch Control Thumb
Shadow](#19676)
  </details>

## Toolbar
- [iOS/Mac Catalyst 26] Fix Shell.ForegroundColor not applied to
ToolbarItems by @SyedAbdulAzeemSF4852 in
#34085
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS26] Shell.ForegroundColor is not applied to
ToolbarItems](#34083)
  </details>

- [Android] VoiceOver on Toolbar Item by @kubaflo in
#29596
  <details>
  <summary>🔧 Fixes</summary>

- [VoiceOver on Toolbar
Item](#29573)
- [SemanticProperties do not work on
ToolbarItems](#23623)
  </details>


<details>
<summary>🧪 Testing (11)</summary>

- [Testing] Additional Feature Matrix Test Cases for CollectionView by
@TamilarasanSF4853 in #32432
- [Testing] Feature Matrix UITest Cases for VisualStateManager by
@LogishaSelvarajSF4525 in #34146
- [Testing] Feature Matrix UITest Cases for Clip by @TamilarasanSF4853
in #34121
- [Testing] Feature matrix UITest Cases for Map Control by
@HarishKumarSF4517 in #31656
- [Testing] Feature matrix UITest Cases for Visual Transform Control by
@HarishKumarSF4517 in #32799
- [Testing] Feature Matrix UITest Cases for Shell Pages by
@NafeelaNazhir in #33945
- [Testing] Feature Matrix UITest Cases for Triggers by
@HarishKumarSF4517 in #34152
- [Testing] Refactoring Feature Matrix UITest Cases for CheckBox Control
by @LogishaSelvarajSF4525 in #34283
- Resolve UI test Build Sample failures - Candidate March 16 by
@Ahamed-Ali in #34442
- Fix the failures in the Candidate branch- March 16 by @Ahamed-Ali in
#34453
  <details>
  <summary>🔧 Fixes</summary>

  - [March 16th, Candidate](#34437)
  </details>
- Fixed the iOS 18.5 Candidate failures (March 16,2026) by @Ahamed-Ali
in #34593
  <details>
  <summary>🔧 Fixes</summary>

  - [March 16th, Candidate](#34437)
  </details>

</details>

<details>
<summary>📦 Other (2)</summary>

- Fixed candidate test failures caused by PR #33428. by @Ahamed-Ali in
#34515
  <details>
  <summary>🔧 Fixes</summary>

- [[.NET10] On Android, there's a big space at the top for I, M and N2 &
N3](#34509)
  </details>
- Revert "[iOS] Button RTL text and image overlap - fix (#29041)" in
b0497af

</details>

<details>
<summary>📝 Issue References</summary>

Fixes #2574, Fixes #4993, Fixes #8486, Fixes #13258, Fixes #14160, Fixes
#14364, Fixes #17799, Fixes #18011, Fixes #18668, Fixes #19676, Fixes
#21044, Fixes #22938, Fixes #23014, Fixes #23623, Fixes #24450, Fixes
#26187, Fixes #26726, Fixes #27377, Fixes #27799, Fixes #27800, Fixes
#28656, Fixes #28784, Fixes #28968, Fixes #29141, Fixes #29394, Fixes
#29535, Fixes #29573, Fixes #29921, Fixes #30085, Fixes #30347, Fixes
#30363, Fixes #30837, Fixes #30862, Fixes #31166, Fixes #31239, Fixes
#31259, Fixes #32016, Fixes #32200, Fixes #32312, Fixes #32650, Fixes
#33114, Fixes #33201, Fixes #33229, Fixes #33316, Fixes #33344, Fixes
#33351, Fixes #33400, Fixes #33407, Fixes #33479, Fixes #33660, Fixes
#33722, Fixes #33829, Fixes #33925, Fixes #33966, Fixes #33967, Fixes
#34083, Fixes #34143, Fixes #34190, Fixes #34247, Fixes #34273, Fixes
#34278, Fixes #34437, Fixes #34509, Fixes #34512

</details>

**Full Changelog**:
main...inflight/candidate
KarthikRajaKalaimani pushed a commit to KarthikRajaKalaimani/maui that referenced this pull request Mar 30, 2026
…true (dotnet#28983)

### Description of Change

On iOS, the `ActivityIndicator` becomes visible even when `IsVisible =
false` and `IsRunning = true`, effectively ignoring the `IsVisible`
property.

**Root Cause**

Visibility is not being correctly mapped in iOS.

By default, `IsVisible` is `true` for all elements, so we must
explicitly manage visibility based on the `IsRunning` value — especially
since it's expected that the `ActivityIndicator` is hidden by default.

The current implementation seems to work because `IsRunning` defaults to
`false`, which calls `StopAnimating()` and hides the native control.
However, if `HidesWhenStopped` is set to `false`, the control remains
visible without animating — which is incorrect.

To fix this, we explicitly update the visibility inside the `IsRunning`
mapper, just as it's done on Android.


<table>
  <tr>
<th>Before Fix</th>
<th>After Fix</th>
</tr>
<tr>
<td>


https://github.com/user-attachments/assets/19482315-e5ba-4c4e-af2a-2e883d6eef35


</td>
<td>


https://github.com/user-attachments/assets/9c05750d-d7ef-445c-9c65-64e6e142cc45


</td>
</tr>
</table>

### Issues Fixed


Closes dotnet#28968

---------

Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-controls-activityindicator ActivityIndicator community ✨ Community Contribution platform/ios s/agent-fix-implemented PR author implemented the agent suggested fix s/agent-fix-pr-picked AI could not beat the PR fix - PR is the best among all candidates s/agent-gate-passed AI verified tests catch the bug (fail without fix, pass with fix) s/agent-review-incomplete AI agent could not complete all phases (blocker, timeout, error) s/agent-reviewed PR was reviewed by AI agent workflow (full 4-phase review)

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

[iOS] [ActivityIndicator] IsRunning ignores IsVisible when set to true