A basic DocumentGroup App presents two back "<" buttons on the navigation bar.

Question

Created Sep ’22

Replies 8

Boosts 5

Views 1.6k

Participants 7

Please has anyone found a workaround for duplicate back buttons appearing on the toolbar of a ContentView launched from a DocumentGroup?

The problem occurs with Xcode 14.0 running a basic DocumentGroup App on iOS 16.0.

To reproduce, simply build a new project using the "Document App" template. Build and run in the iOS/iPadOS simulator or on an iOS/iPadOS device.

Two back buttons appear. Only one functions. I've not found a way to eliminate the dud.

This problem has occurred throughout the Xcode 14.0 beta program.

Boost

Answer 1

Kasuist OP

Sep ’22

Did you report this, because I'm having the exact same issue. Made a ticket, and nothing...

1

Answer 2

noid_sandro OP

Sep ’22

I have the same issue. Didn’t happen on iOS 15. i haven’t found a workaround so far sadly.

1

Answer 3

noid_sandro OP

Sep ’22

Ok I just accidentally found a workaround, use with caution because I haven't checked yet what exactly it does (but it removes the additional back button). Adding .toolbarRole(.automatic) to the content view fixes it (or any of those roles).

DocumentGroup(newDocument: TestDocAppDocument()) { file in
            ContentView(document: file.$document) 
                 .toolbarRole(.automatic)
}

4

Answer 4

cjhunt OP

Sep ’22

Nice one. Thank you! It looks as if ".browser", ".automatic", ".navigationStack" each eliminate the extra (left hand) back button nicely. Choosing ".editor" is the odd-ball. I've not made sense of the documentation on this - but - for now I'll run with .automatic. Thanks again.

1

Answer 5

Uberfish OP

Nov ’22

Great job. Had just started rewriting my app to 'fileImporter'

0

Answer 6

dragon_lucky_ OP

Dec ’22

This bug seems to be fixed in iOS 16.2

0

Answer 7

JJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJ OP

Apr ’24

Try this:

NavigationStack {
  // ...
}
.navigationBarHidden(true)

0

Answer 8

JJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJ OP

May ’24

Don't use NavigationView, use NavigationStack

0