xamarin/Xamarin.Forms

[iOS] Navigation bar back button only shows arrow without text on iOS 10

Open

#5,574 opened on Mar 15, 2019

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)C# (1,926 forks)batch import
e/3 :clock3:help wantedinactivep/iOS 🍎t/bug :bug:up-for-grabs

Repository metrics

Stars
 (5,644 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Description

The default navigation bar back button that shows whenever a navigation page has a previous page does not show the default text.

On iOS 11 and above it shows the previous page's title, or the "Back" text whenever there isn't enough space to on the navbar to display the whole text, and if the space is still not for even the "Back" text to show, it only shows a back arrow.

Steps to Reproduce

  1. Create a Xamarin.Forms project.
  2. Add an additional navigation page and navigate to it from the main page.
  3. Observe navigation bar back button behavior and appearance on iOS 10 and iOS 11+.

Expected Behavior

Should show the previous page's title or "Back" or the Back arrow only depending on the space provided on iOS 10.

Actual Behavior

Only shows the Back arrow on iOS 10.

Basic Information

  • Version with issue: Xamarin.Forms 3.4+.
  • Last known good version: Not sure
  • IDE: Visual Studio 2017 on Mac
  • Platform Target Frameworks:
    • iOS: iOS 10.0
  • Affected Devices: iOS 10

Screenshots

iOS 10 iOS 10 Scr

iOS 11 and above iOS 12 Scr

Contributor guide

Research direction
Investigate the back button rendering logic in Xamarin.Forms for iOS. Compare the UINavigationItem appearance between iOS 10 and iOS 11+. Check for any conditional code that sets the back button title based on iOS version, and ensure the title or default 'Back' text is shown on iOS 10.
Tech stack
csharp
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Xamarin.FormsiOS development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60