[iOS 26] Fix back button color not applied for NavigationPage#34326
[iOS 26] Fix back button color not applied for NavigationPage#34326kubaflo merged 2 commits intodotnet:inflight/currentfrom
Conversation
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 34326Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 34326" |
|
Hey there @@Shalini-Ashokan! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
There was a problem hiding this comment.
Pull request overview
This PR fixes an iOS 26 regression where setting a color for the navigation back button (text and arrow) has no effect due to iOS 26's Liquid Glass navigation bar no longer honoring the standard TintColor property for back button elements.
Changes:
- On iOS 26+, applies back button color through the navigation bar appearance's
BackButtonAppearanceconfiguration, setting text color via title text attributes and manually tinting the back arrow image withAlwaysOriginalrendering mode. - Updates the existing screenshot test to remove tolerance/retryTimeout parameters and adds a new iOS 26-specific reference snapshot.
- Refactors the
useCustomColorlogic into a local variable for clarity.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
src/Controls/src/Core/Compatibility/Handlers/NavigationPage/iOS/NavigationRenderer.cs |
Adds iOS 26+ workaround to apply back button color via UIBarButtonItemAppearance and custom tinted back arrow image instead of relying on TintColor. |
src/Controls/tests/TestCases.Shared.Tests/Tests/FeatureMatrix/NavigationPageFeatureTests.cs |
Removes tolerance and retryTimeout parameters from VerifyScreenshot() call in the combined bar background/text/icon color test. |
src/Controls/tests/TestCases.iOS.Tests/snapshots/ios-26/Combine_BarBackgroundColor_TextColor_IconColor_Visual.png |
New reference screenshot for iOS 26 showing the expected back button color rendering. |
src/Controls/tests/TestCases.Shared.Tests/Tests/FeatureMatrix/NavigationPageFeatureTests.cs
Show resolved
Hide resolved
src/Controls/src/Core/Compatibility/Handlers/NavigationPage/iOS/NavigationRenderer.cs
Show resolved
Hide resolved
src/Controls/src/Core/Compatibility/Handlers/NavigationPage/iOS/NavigationRenderer.cs
Show resolved
Hide resolved
🤖 AI Summary📊 Expand Full Review🔍 Pre-Flight — Context & Validation📝 Review Session — Address review feedback: remove iOS 26 skip and fix naming ·
|
| File:Line | Issue | Status |
|---|---|---|
NavigationPageFeatureTests.cs:252-254 |
SetIconColor_Red_Purple_Default_Visual still has Assert.Ignore for iOS 26 |
|
Issue17228.cs:20-22 |
CustomBackButtonShouldBeRed still has Assert.Ignore for iOS 26 |
Copilot reviewer flags (from inline comments, now mostly addressed):
- ✅
Assert.IgnoreinCombine_BarBackgroundColor_TextColor_IconColor_Visual- FIXED - ✅
backimagenaming - FIXED ⚠️ Double blank line - still present at line 951-952?
Fix Candidates Table
| # | Source | Approach | Test Result | Files Changed | Notes |
|---|---|---|---|---|---|
| PR | PR #34326 | Use UIBarButtonItemAppearance + tinted AlwaysOriginal image for iOS 26+; removed Assert.Ignore from primary test |
⏳ PENDING (Gate) | NavigationRenderer.cs (+41/-3), NavigationPageFeatureTests.cs (+1/-5) |
Original PR; 2 other tests still ignore iOS 26 |
🚦 Gate — Test Verification
📝 Review Session — Address review feedback: remove iOS 26 skip and fix naming · 1d2c8a0
Result: ✅ PASSED
Platform: iOS (ios-26)
Mode: Full Verification
Verification Results
| Check | Expected | Actual | Result |
|---|---|---|---|
| Tests WITHOUT fix | FAIL | FAIL | ✅ |
| Tests WITH fix | PASS | PASS | ✅ |
What Happened
- Tests FAIL without the fix (bug is present on iOS 26)
- Tests PASS with the fix (fix correctly applies back button color via
UIBarButtonItemAppearance)
Test: Combine_BarBackgroundColor_TextColor_IconColor_Visual
File: NavigationPageFeatureTests.cs
Note: The Assert.Ignore for iOS 26 was removed in commit 1d2c8a01, enabling the test to properly exercise and validate the fix.
🔧 Fix — Analysis & Comparison
📝 Review Session — Address review feedback: remove iOS 26 skip and fix naming · 1d2c8a0
Fix Candidates
| # | Source | Approach | Test Result | Files Changed | Notes |
|---|---|---|---|---|---|
| PR | PR #34326 | UIBarButtonItemAppearance.BackButtonAppearance on 3 appearance variants (compact/standard/scrollEdge) + NavigationBar.BackIndicatorImage with AlwaysOriginal rendering mode |
✅ PASS (Gate) | NavigationRenderer.cs (+41/-3) |
Original PR; most targeted approach |
| 1 | try-fix (claude-sonnet-4.6) | UINavigationBarAppearance.ButtonAppearance on 3 variants + SetBackIndicatorImage per appearance |
✅ PASS | NavigationRenderer.cs |
Broader than needed - affects ALL bar buttons, not just back button |
| 2 | try-fix (claude-opus-4.6) | SetTitleTextAttributes per ViewController's BackBarButtonItem + NavigationBar.BackIndicatorImage |
✅ PASS | NavigationRenderer.cs |
Misses newly pushed/popped VCs; per-VC complexity |
| 3 | try-fix (gpt-5.2) | Custom LeftBarButtonItem (UIButton with chevron.backward) replacing system back button |
✅ PASS | NavigationRenderer.cs |
Loses native iOS swipe gesture, long-press back navigation, and system accessibility behavior |
| 4 | try-fix (gpt-5.3-codex) | Runtime subview traversal to recolor back-button elements in ViewDidLayoutSubviews |
✅ PASS | NavigationRenderer.cs |
Fragile - relies on undocumented private view hierarchy; will break on future iOS updates |
| 5 | try-fix (gemini-3-pro-preview) | Iterate NavigationBar.Items, set TintColor + SetTitleTextAttributes on each BackBarButtonItem + BackIndicatorImage with AlwaysOriginal |
✅ PASS | NavigationRenderer.cs |
Only affects currently-loaded VCs, misses future navigation items |
| 6 | try-fix (gpt-5.2 R2) | UIBarButtonItem.AppearanceWhenContainedIn(UINavigationBar) global proxy |
✅ PASS | NavigationRenderer.cs |
Global side effect - modifies ALL UIBarButtonItems in ALL UINavigationBars app-wide; cannot properly reset per-instance |
Cross-Pollination Results
| Round | Model | Response |
|---|---|---|
| 2 | claude-sonnet-4.6 | Suggested NavigationBar.TintColor instance - already the existing BROKEN code, not new |
| 2 | claude-opus-4.6 | NO NEW IDEAS |
| 2 | gpt-5.2 | Said NEW IDEA but provided no description |
| 2 | gpt-5.3-codex | Suggested BackButtonDisplayMode.Minimal - changes UX behavior, not color fix |
| 2 | gemini-3-pro-preview | Suggested colored UIImage AlwaysOriginal - same as PR fix |
| 3 | claude-sonnet-4.6 | Suggested UINavigationBar subclass - overly complex |
| 3 | claude-opus-4.6 | NO NEW IDEAS |
| 3 | gpt-5.2 | Suggested CompactScrollEdgeAppearance (4th variant) - minor variant of PR fix |
| 3 | gpt-5.3-codex | NO NEW IDEAS |
| 3 | gemini-3-pro-preview | Suggested UINavigationControllerDelegate willShowViewController - variant of Attempt 4 |
Exhausted: Yes (3 rounds completed, max reached)
Selected Fix: PR's fix — BackButtonAppearance is the most semantically correct API (specifically targets back buttons vs. all bar buttons), is scoped to the specific NavigationBar instance (no global side effects from Attempt 6), and properly handles both set and reset paths. All independent alternatives either have broader scope, global side effects, fragile runtime dependency on private view hierarchy, or lose native iOS system behavior.
📋 Report — Final Recommendation
📝 Review Session — Address review feedback: remove iOS 26 skip and fix naming · 1d2c8a0
✅ Final Recommendation: APPROVE
Summary
PR #34326 fixes a genuine iOS 26 regression where the navigation back button color (text and chevron arrow) was no longer applied due to Apple's iOS 26 Liquid Glass rendering pipeline change. The PR implements the correct fix using UIBarButtonItemAppearance.BackButtonAppearance, validated through Gate testing and independently confirmed by 6 alternative try-fix approaches across 5 AI models.
Root Cause
iOS 26's Liquid Glass navigation bar changed its rendering pipeline so that UINavigationBar.TintColor no longer affects back button elements (text label and chevron arrow). The fix applies the color through UIBarButtonItemAppearance with BackButtonAppearance on all three appearance contexts (compact, standard, scrollEdge), and manually tints the chevron.backward system image with AlwaysOriginal rendering mode to bypass UIKit's overriding of custom tints.
Fix Quality
The implementation is correct and follows established patterns:
- ✅ Uses
BackButtonAppearance(semantically correct — targets only back buttons, not all bar buttons) - ✅ Instance-scoped to the specific
NavigationBar(no global side effects) - ✅ Applies to all three standard appearance variants (compact, standard, scrollEdge)
- ✅ Properly resets appearance when no custom color is set (avoids stale state)
- ✅ Guarded by
OperatingSystem.IsIOSVersionAtLeast(26)(backward compatible) - ✅ Naming fixed (
backImage) per codebase conventions - ✅
Assert.Ignoreremoved fromCombine_BarBackgroundColor_TextColor_IconColor_Visualtest - ✅ New iOS 26-specific snapshot added
Remaining Items (Non-Blocking)
Two tests still have Assert.Ignore for iOS 26 but they are separate issues not directly fixed by this PR's implementation:
SetIconColor_Red_Purple_Default_Visual— tests icon color states (red, purple, default) separately; may need additional workIssue17228.CustomBackButtonShouldBeRed— tests back button on a different page; may be covered but not verified
These are acceptable to address in follow-up PRs.
Alternative Approaches Explored
6 independent try-fix approaches all passed, validating that the iOS 26 rendering pipeline can be fixed at multiple layers. The PR's approach using BackButtonAppearance is the most targeted and semantically correct:
| Approach | Tradeoff |
|---|---|
ButtonAppearance (Attempt 1) |
Affects ALL bar buttons, broader than needed |
Per-BackBarButtonItem attributes (Attempt 2) |
Misses future pushed VCs |
Custom LeftBarButtonItem (Attempt 3) |
Loses native iOS swipe/long-press behavior |
| Runtime subview traversal (Attempt 4) | Fragile, depends on private view hierarchy |
NavigationBar.Items iteration (Attempt 5) |
Only affects currently-loaded VCs |
AppearanceWhenContainedIn global proxy (Attempt 6) |
Global side effect across all nav bars in app |
PR's BackButtonAppearance approach wins on all criteria: targeted scope, no global side effects, proper set/reset lifecycle, and uses the iOS-designated API for back button appearance.
PR Finalize Check
- ✅ Title accurately reflects implementation:
[iOS 26] Fix back button color not applied for NavigationPage - ✅ Description matches actual changes (UIBarButtonItemAppearance + image tinting)
- ✅ NOTE block present at top of description
- ✅ Before/after screenshots included
- ✅ Code is backward compatible (no impact on iOS < 26)
🔧 Try-Fix Analysis: ✅ 1 passed
✅ Fix 5
Approach: Explicit Back Indicator & Item Tinting
This approach manually constructs the back button appearance by:
- Replacing the system back indicator with a specifically tinted "chevron.backward" system image (using
AlwaysOriginalrendering mode). - Iterating through the navigation stack and explicitly setting the
BackBarButtonItem.TintColorfor each item, creating the item if it doesn't exist.
Different from existing fix:
- PR fix used
UIBarButtonItemAppearance(Appearance API). - Attempt 1 used
UINavigationBarAppearance(Appearance API). - Attempt 2 set
TitleTextAttributeson existing items. - Attempt 3 replaced the
LeftBarButtonItem(replacing the back button concept entirely). - Attempt 4 used subview traversal.
This approach works by leveraging the UINavigationBar.BackIndicatorImage property with a pre-tinted image (bypassing the bar's tint color) and enforcing the item's tint color directly on the instance.
diff --git a/src/Controls/src/Core/Compatibility/Handlers/NavigationPage/iOS/NavigationRenderer.cs b/src/Controls/src/Core/Compatibility/Handlers/NavigationPage/iOS/NavigationRenderer.cs
index a120b1cdee..de3753a1d9 100644
--- a/src/Controls/src/Core/Compatibility/Handlers/NavigationPage/iOS/NavigationRenderer.cs
+++ b/src/Controls/src/Core/Compatibility/Handlers/NavigationPage/iOS/NavigationRenderer.cs
@@ -943,9 +943,42 @@ namespace Microsoft.Maui.Controls.Handlers.Compatibility
if (iconColor == null)
iconColor = barTextColor;
- NavigationBar.TintColor = iconColor == null || NavPage.OnThisPlatform().GetStatusBarTextColorMode() == StatusBarTextColorMode.DoNotAdjust
+ var platformColor = iconColor == null || NavPage.OnThisPlatform().GetStatusBarTextColorMode() == StatusBarTextColorMode.DoNotAdjust
? UINavigationBar.Appearance.TintColor
: iconColor.ToPlatform();
+
+ NavigationBar.TintColor = platformColor;
+
+ // Attempt 5: Explicit Back Indicator & Item Tinting
+ if (iconColor != null && OperatingSystem.IsIOSVersionAtLeast(13))
+ {
+ // 1. Force the chevron color by using a pre-tinted image
+ var backImage = UIImage.GetSystemImage("chevron.backward");
+ if (backImage != null)
+ {
+ // Tint the image and force AlwaysOriginal so it ignores the broken Bar TintColor
+ var tintedImage = backImage.ApplyTintColor(platformColor).ImageWithRenderingMode(UIImageRenderingMode.AlwaysOriginal);
+ NavigationBar.BackIndicatorImage = tintedImage;
+ NavigationBar.BackIndicatorTransitionMaskImage = tintedImage;
+ }
+
+ // 2. Force the text color by iterating items and setting TintColor on BackBarButtonItem
+ foreach (var item in NavigationBar.Items)
+ {
+ if (item.BackBarButtonItem == null)
+ {
+ // Create a back button item if one doesn't exist, using the item's title
+ // This ensures we have an object to attach the color to
+ item.BackBarButtonItem = new UIBarButtonItem(item.Title ?? "Back", UIBarButtonItemStyle.Plain, null, null);
+ }
+
+ // Explicitly set the TintColor on the item instance
+ item.BackBarButtonItem.TintColor = platformColor;
+
+ // Also set attributes just in case TintColor alone isn't enough for text
+ item.BackBarButtonItem.SetTitleTextAttributes(new UIStringAttributes { ForegroundColor = platformColor }, UIControlState.Normal);
+ }
+ }
}
void SetStatusBarStyle()
Analysis
Result: Pass
What happened:
The test Combine_BarBackgroundColor_TextColor_IconColor_Visual passed successfully.
Initially, the test failed to compile because EstablishBrokenBaseline.ps1 reverted VisualRegressionTester.cs (infrastructure) which UITest.cs depended on. Restoring VisualRegressionTester.cs resolved the compilation error, allowing the test to run and verify the fix.
Why it worked:
The fix addresses the issue where UINavigationBar.TintColor is ignored by the system back button on newer iOS versions (simulated context).
- Chevron: By retrieving the system back image (
chevron.backward), explicitly tinting it with the desired color, and setting it asBackIndicatorImagewithRenderingMode.AlwaysOriginal, we bypass the system's broken tinting logic. - Text: By iterating through the navigation stack and explicitly creating/updating the
BackBarButtonItemfor each item, and setting theTintColorproperty directly on the item instance, we ensure the text color is applied correctly. This instance-level setting often takes precedence or works where global/container appearance proxies fail.
Insights:
- Explicitly managing the
BackBarButtonIteminstance allows for more granular control than relying on implicit system behavior. - Using
AlwaysOriginalrendering mode for the back indicator image is a reliable workaround when propagation is broken. - The legacy approach was considered but the direct instance modification proved effective and simpler to target specific items in the stack.
📋 Expand PR Finalization Review
Title: ✅ Good
Current: [iOS 26] Fix back button color not applied for NavigationPage
Description: ✅ Excellent
Description needs updates. See details below.
Code Review: ⚠️ Issues Found
Code Review — PR #34326
PR: #34326 - [iOS 26] Fix back button color not applied for NavigationPage
🔴 Critical Issues
None.
🟡 Suggestions
1. VerifyScreenshot() — Tolerance and Retry Removed
File: src/Controls/tests/TestCases.Shared.Tests/Tests/FeatureMatrix/NavigationPageFeatureTests.cs
Change:
// Before:
VerifyScreenshot(tolerance: 0.5, retryTimeout: TimeSpan.FromSeconds(2));
// After:
VerifyScreenshot();Observation: The original tolerance: 0.5 and retryTimeout: TimeSpan.FromSeconds(2) were added to accommodate rendering variance and animation timing. Their removal is appropriate if the fix makes iOS 26 back button rendering fully deterministic, but could reintroduce flakiness if there is any sub-pixel variation in the iOS 26 Liquid Glass rendering across simulator versions or screen resolutions.
Recommendation: If CI confirms consistent baseline snapshot matching, this change is fine. If flakiness appears in CI runs, restore retryTimeout: TimeSpan.FromSeconds(2) as per the UI testing guidelines which recommend retryTimeout over tolerance for timing issues.
Risk: Low — this is a test-only change and the worst case is a revert back to the previous VerifyScreenshot arguments.
✅ Looks Good
Core Fix Approach
The fix correctly identifies and uses the right API for iOS 26+ Liquid Glass:
// iOS 26+ Liquid Glass ignores TintColor for the back button; apply via appearance instead.
if (OperatingSystem.IsIOSVersionAtLeast(26) || OperatingSystem.IsMacCatalystVersionAtLeast(26))
{
if (useCustomColor)
{
var backColor = iconColor.ToPlatform();
var colorAttributes = NSDictionary<NSString, NSObject>.FromObjectsAndKeys(
new NSObject[] { backColor }, new NSString[] { UIStringAttributeKey.ForegroundColor });
var appearance = new UIBarButtonItemAppearance(UIBarButtonItemStyle.Plain);
appearance.Normal.TitleTextAttributes = colorAttributes;
appearance.Highlighted.TitleTextAttributes = colorAttributes;
NavigationBar.CompactAppearance.BackButtonAppearance = appearance;
NavigationBar.StandardAppearance.BackButtonAppearance = appearance;
NavigationBar.ScrollEdgeAppearance.BackButtonAppearance = appearance;
...- ✅
UIBarButtonItemAppearance.BackButtonAppearanceis the correct API to override back button styling on iOS 26 Liquid Glass whereTintColoris no longer respected. - ✅ Both
NormalandHighlightedstates are set for consistent color in both pressed and unpressed states. - ✅ All three appearance contexts (
CompactAppearance,StandardAppearance,ScrollEdgeAppearance) are set — consistent with the existing pattern used throughout the renderer for other appearance properties (e.g.,ShadowColor,TitleTextAttributes).
AlwaysOriginal Rendering Mode for Back Arrow Image
var tinted = backImage.ApplyTintColor(backColor).ImageWithRenderingMode(UIImageRenderingMode.AlwaysOriginal);
NavigationBar.BackIndicatorImage = tinted;
NavigationBar.BackIndicatorTransitionMaskImage = tinted;- ✅
AlwaysOriginalrendering mode is correctly used to prevent the system from reapplying its own tint color on top of the pre-tinted image. Without it, iOS would override the color. - ✅ Both
BackIndicatorImageandBackIndicatorTransitionMaskImageare set — matching documentation requirements for the back button chevron. - ✅ Null check on
backImage(if (backImage is not null)) guards against the unlikely case where the system image is unavailable.
Cleanup Path When No Custom Color
else
{
NavigationBar.CompactAppearance.BackButtonAppearance = null;
NavigationBar.StandardAppearance.BackButtonAppearance = null;
NavigationBar.ScrollEdgeAppearance.BackButtonAppearance = null;
NavigationBar.BackIndicatorImage = null;
NavigationBar.BackIndicatorTransitionMaskImage = null;
}- ✅ Properly resets to system defaults when no custom color is configured.
- ✅ Null-setting
BackButtonAppearancelets the system use default Liquid Glass styling.
Refactored Condition
// Before (one-liner):
NavigationBar.TintColor = iconColor == null || NavPage.OnThisPlatform().GetStatusBarTextColorMode() == StatusBarTextColorMode.DoNotAdjust
? UINavigationBar.Appearance.TintColor
: iconColor.ToPlatform();
// After (extracted):
var useCustomColor = iconColor != null && NavPage.OnThisPlatform().GetStatusBarTextColorMode() != StatusBarTextColorMode.DoNotAdjust;
NavigationBar.TintColor = useCustomColor
? iconColor.ToPlatform()
: UINavigationBar.Appearance.TintColor;- ✅ Extracting
useCustomColorimproves readability and eliminates the need to duplicate the condition check in the iOS 26 block below. Good refactoring.
Test Update
- ✅ Correctly removes
Assert.Ignore("Ignored due to a bug issue in iOS 26")— this skip was a temporary workaround for [iOS] Color not applied to the Back button text or image on iOS 26 #33966 and should be removed now that the bug is fixed. - ✅ New iOS 26 baseline snapshot
Combine_BarBackgroundColor_TextColor_IconColor_Visual.pngadded tosnapshots/ios-26/— provides visual regression protection for the fixed behavior.
Backward Compatibility
- ✅ The entire iOS 26 block is gated behind
OperatingSystem.IsIOSVersionAtLeast(26) || OperatingSystem.IsMacCatalystVersionAtLeast(26). The pre-iOS 26 code path is completely unchanged. - ✅ No public API changes.
|
Hi! Could you please resolve conflicts, so that we can merge? |
1d2c8a0 to
064ab0f
Compare
- Remove Assert.Ignore for iOS 26 since this PR fixes dotnet#33966; the test should now validate the fix on iOS 26 - Rename 'backimage' to 'backImage' for camelCase consistency - Remove extra blank line Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
064ab0f to
b00e514
Compare
@kubaflo, The conflicts have been resolved. |
<!-- 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 On iOS 26, setting a color for the navigation back button text or arrow image has no effect. ### Root Cause iOS 26's Liquid Glass navigation bar no longer honors the standard tint color property for back button elements. Apple changed the rendering pipeline so the back button and text ignore the previously used tint color API. ### Description of Change On iOS 26+, apply the back button color through the navigation bar appearance's back button appearance configuration instead. Set the text color via title text attributes on the back button appearance, and manually tint the back arrow image using the desired color with always-original rendering mode to prevent the system from overriding it. Validated the behavior in the following platforms - [x] Android - [x] Windows - [x] iOS - [x] Mac ### Issues Fixed Fixes #33966 ### Output ScreenShot | Before | After | |---------|--------| | <img width="357" height="829" alt="Before-Fix" src="https://github.com/user-attachments/assets/7ef9e5ab-44ba-4aab-9bbf-40f9135e3003" /> | <img width="357" height="829" alt="After-Fix" src="https://github.com/user-attachments/assets/991e11c3-f76e-40c4-99ac-4ea1a6bf9cf0" /> | --------- Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
<!-- 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 On iOS 26, setting a color for the navigation back button text or arrow image has no effect. ### Root Cause iOS 26's Liquid Glass navigation bar no longer honors the standard tint color property for back button elements. Apple changed the rendering pipeline so the back button and text ignore the previously used tint color API. ### Description of Change On iOS 26+, apply the back button color through the navigation bar appearance's back button appearance configuration instead. Set the text color via title text attributes on the back button appearance, and manually tint the back arrow image using the desired color with always-original rendering mode to prevent the system from overriding it. Validated the behavior in the following platforms - [x] Android - [x] Windows - [x] iOS - [x] Mac ### Issues Fixed Fixes #33966 ### Output ScreenShot | Before | After | |---------|--------| | <img width="357" height="829" alt="Before-Fix" src="https://github.com/user-attachments/assets/7ef9e5ab-44ba-4aab-9bbf-40f9135e3003" /> | <img width="357" height="829" alt="After-Fix" src="https://github.com/user-attachments/assets/991e11c3-f76e-40c4-99ac-4ea1a6bf9cf0" /> | --------- Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
<!-- 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 On iOS 26, setting a color for the navigation back button text or arrow image has no effect. ### Root Cause iOS 26's Liquid Glass navigation bar no longer honors the standard tint color property for back button elements. Apple changed the rendering pipeline so the back button and text ignore the previously used tint color API. ### Description of Change On iOS 26+, apply the back button color through the navigation bar appearance's back button appearance configuration instead. Set the text color via title text attributes on the back button appearance, and manually tint the back arrow image using the desired color with always-original rendering mode to prevent the system from overriding it. Validated the behavior in the following platforms - [x] Android - [x] Windows - [x] iOS - [x] Mac ### Issues Fixed Fixes #33966 ### Output ScreenShot | Before | After | |---------|--------| | <img width="357" height="829" alt="Before-Fix" src="https://github.com/user-attachments/assets/7ef9e5ab-44ba-4aab-9bbf-40f9135e3003" /> | <img width="357" height="829" alt="After-Fix" src="https://github.com/user-attachments/assets/991e11c3-f76e-40c4-99ac-4ea1a6bf9cf0" /> | --------- Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
### 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>
<!-- 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 On iOS 26, setting a color for the navigation back button text or arrow image has no effect. ### Root Cause iOS 26's Liquid Glass navigation bar no longer honors the standard tint color property for back button elements. Apple changed the rendering pipeline so the back button and text ignore the previously used tint color API. ### Description of Change On iOS 26+, apply the back button color through the navigation bar appearance's back button appearance configuration instead. Set the text color via title text attributes on the back button appearance, and manually tint the back arrow image using the desired color with always-original rendering mode to prevent the system from overriding it. Validated the behavior in the following platforms - [x] Android - [x] Windows - [x] iOS - [x] Mac ### Issues Fixed Fixes #33966 ### Output ScreenShot | Before | After | |---------|--------| | <img width="357" height="829" alt="Before-Fix" src="https://github.com/user-attachments/assets/7ef9e5ab-44ba-4aab-9bbf-40f9135e3003" /> | <img width="357" height="829" alt="After-Fix" src="https://github.com/user-attachments/assets/991e11c3-f76e-40c4-99ac-4ea1a6bf9cf0" /> | --------- Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
### 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>
<!-- 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 On iOS 26, setting a color for the navigation back button text or arrow image has no effect. ### Root Cause iOS 26's Liquid Glass navigation bar no longer honors the standard tint color property for back button elements. Apple changed the rendering pipeline so the back button and text ignore the previously used tint color API. ### Description of Change On iOS 26+, apply the back button color through the navigation bar appearance's back button appearance configuration instead. Set the text color via title text attributes on the back button appearance, and manually tint the back arrow image using the desired color with always-original rendering mode to prevent the system from overriding it. Validated the behavior in the following platforms - [x] Android - [x] Windows - [x] iOS - [x] Mac ### Issues Fixed Fixes #33966 ### Output ScreenShot | Before | After | |---------|--------| | <img width="357" height="829" alt="Before-Fix" src="https://github.com/user-attachments/assets/7ef9e5ab-44ba-4aab-9bbf-40f9135e3003" /> | <img width="357" height="829" alt="After-Fix" src="https://github.com/user-attachments/assets/991e11c3-f76e-40c4-99ac-4ea1a6bf9cf0" /> | --------- Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
### 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>
- 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>
- 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>
## 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
On iOS 26+, Apple's liquid glass tab bar compositing pipeline ignores UITabBarAppearance Normal state (TitleTextAttributes, IconColor) AND UITabBar.UnselectedItemTintColor for visual rendering, even though the properties are stored correctly. This caused TabbedPage.BarTextColor and Shell.TabBarUnselectedColor to have no visual effect on unselected tabs. Fix: Bypass the tint pipeline entirely on iOS 26+ by using pre-colored images with AlwaysOriginal rendering mode (via UIImage.ApplyTintColor), which bakes the color into image pixel data. This is the same approach used for the iOS 26 back button color fix (PR #34326). Also set per-item SetTitleTextAttributes for text color. Cache original template images in a ConditionalWeakTable to avoid quality degradation from repeated AlwaysOriginal→Template round-trips. For Shell: Early-return in SafeShellTabBarAppearanceTracker on iOS 26+, skipping the full appearance pipeline. Cache pending colors for re-application in UpdateLayout since liquid glass resets properties. For TabbedPage: Cache effective colors in TabbedRenderer and re-apply in ViewDidLayoutSubviews. Pre-iOS 26 behavior is unchanged. Fixes #32125 Fixes #34605 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
On iOS 26+, Apple's liquid glass tab bar compositing pipeline ignores UITabBarAppearance Normal state (TitleTextAttributes, IconColor) AND UITabBar.UnselectedItemTintColor for visual rendering, even though the properties are stored correctly. This caused TabbedPage.BarTextColor and Shell.TabBarUnselectedColor to have no visual effect on unselected tabs. Fix: Bypass the tint pipeline entirely on iOS 26+ by using pre-colored images with AlwaysOriginal rendering mode (via UIImage.ApplyTintColor), which bakes the color into image pixel data. This is the same approach used for the iOS 26 back button color fix (PR #34326). Also set per-item SetTitleTextAttributes for text color. Cache original template images in a ConditionalWeakTable to avoid quality degradation from repeated AlwaysOriginal→Template round-trips. For Shell: Early-return in SafeShellTabBarAppearanceTracker on iOS 26+, skipping the full appearance pipeline. Cache pending colors for re-application in UpdateLayout since liquid glass resets properties. For TabbedPage: Cache effective colors in TabbedRenderer and re-apply in ViewDidLayoutSubviews. Pre-iOS 26 behavior is unchanged. Fixes #32125 Fixes #34605 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…#34326) <!-- 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 On iOS 26, setting a color for the navigation back button text or arrow image has no effect. ### Root Cause iOS 26's Liquid Glass navigation bar no longer honors the standard tint color property for back button elements. Apple changed the rendering pipeline so the back button and text ignore the previously used tint color API. ### Description of Change On iOS 26+, apply the back button color through the navigation bar appearance's back button appearance configuration instead. Set the text color via title text attributes on the back button appearance, and manually tint the back arrow image using the desired color with always-original rendering mode to prevent the system from overriding it. Validated the behavior in the following platforms - [x] Android - [x] Windows - [x] iOS - [x] Mac ### Issues Fixed Fixes dotnet#33966 ### Output ScreenShot | Before | After | |---------|--------| | <img width="357" height="829" alt="Before-Fix" src="https://github.com/user-attachments/assets/7ef9e5ab-44ba-4aab-9bbf-40f9135e3003" /> | <img width="357" height="829" alt="After-Fix" src="https://github.com/user-attachments/assets/991e11c3-f76e-40c4-99ac-4ea1a6bf9cf0" /> | --------- Co-authored-by: Jakub Florkowski <kubaflo123@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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 from this PR and let us know in a comment if this change resolves your issue. Thank you!
Issue Details
On iOS 26, setting a color for the navigation back button text or arrow image has no effect.
Root Cause
iOS 26's Liquid Glass navigation bar no longer honors the standard tint color property for back button elements. Apple changed the rendering pipeline so the back button and text ignore the previously used tint color API.
Description of Change
On iOS 26+, apply the back button color through the navigation bar appearance's back button appearance configuration instead. Set the text color via title text attributes on the back button appearance, and manually tint the back arrow image using the desired color with always-original rendering mode to prevent the system from overriding it.
Validated the behavior in the following platforms
Issues Fixed
Fixes #33966
Output ScreenShot