Xamarin.forms: GTK navigation is broken

Created on 14 Nov 2018  路  12Comments  路  Source: xamarin/Xamarin.Forms

Description

Unable to switch back from the child page

Steps to Reproduce

  1. Create navigation page
  2. Click on link to child page

Expected Behavior

The navigation bar is visible

Actual Behavior

The navigation bar is missed

Basic Information

  • Version with issue: 3.5

Screenshots

WPF:
image

GTK:
image

gtk

All 12 comments

I'm having the same issue with GTK.

I have the feeling that it is related to https://github.com/xamarin/Xamarin.Forms/issues/4713
Let's review this to try to fix the Issue.

@VladislavAntonyuk can you test again with 4.x?

@knocte , still broken on the latest night build. Toolbar is missed for example in master details page

I had the same problem, does this commit : https://github.com/nels83/Xamarin.Forms/commit/627c7838f6931473faa2d43c0bb4ce62cb9f5ade fixes it for you ?

@VladislavAntonyuk the commit that @nels83 asked you to test is not in Xamarin.Forms master, but his fork.

@nels83 , @knocte yes, the your commit fixes the problem. Please, submit a pull request

This issue can be closed then, as it was merged in master here: https://github.com/xamarin/Xamarin.Forms/commit/7a1434b74784853cd1ddeb1746b4e6327faa0acc

Strange, this issue should've been closed when merging the PR. Well, here we go!

this issue should've been closed when merging the PR

For that to happen, the commit message needs to include the string "fixes #4409" (note I said the commit message, not the PR description).

@jfversluis , Please reopen the issue. it is only half fixed.
@nels83 The issue is fixed for the master page.
Steps to reproduce.

  1. On master page and detail page add a button to the navigation bar
  2. navigate from master page to detail page. Navigation bar is displayed (as expected)
  3. Click on the back button and navigate again to the detail page

AR: Navigation bar is not displayed
ER: Navigation bar is displayed

@VladislavAntonyuk if yours are different steps to reproduce than the OP's, then it's a different bug, please open a new one.

Was this page helpful?
0 / 5 - 0 ratings