xamarin/Xamarin.Forms

Binding not working in titleview using xamarin.forms ios but works in android

Open

#4,520 opened on Nov 23, 2018

View on GitHubContributor guide
 (5 comments) (0 reactions) (0 assignees)C# (1,926 forks)batch import
a/binding ⛓a/titleviewe/2 :clock2:good first issuehelp wantedinactivep/iOS 🍎t/bug :bug:up-for-grabs

Repository metrics

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

Description

I am using xamarin.forms (3.3.0.967583) version for developing application. In xamarin.forms iOS application I am unable to bind property from MVVM to xaml in titleview. But its working in Android application. I am not going to attach my code. I also see other related issues but not helping. See below sample code.

<NavigationPage.TitleView>
    <StackLayout HorizontalOptions="Start" 
        VerticalOptions="Center" 
        Margin="0" 
        Padding="{OnPlatform iOS='25,0,0,0', Android=0}">        
        <Label 
            Text="{Binding SelectedProduct.Title, 
            Mode=TwoWay}"
            TextColor="White" 
            FontSize="{StaticResource LargeFontSize}" 
            FontFamily="{StaticResource OpenSansRegular}" 
            VerticalTextAlignment="Center" />
    </StackLayout>
</NavigationPage.TitleView>

Contributor guide

Research direction
Investigate why binding in NavigationPage.TitleView fails on iOS but works on Android. Check Xamarin.Forms source code for platform specific rendering of TitleView, especially on iOS. Verify if the BindingContext is properly set in the TitleView hierarchy.
Tech stack
csharp
Domain
mobile dev
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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.
Needs investigation
Prerequisites
C#Xamarin.Forms
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55