IssueTracker

Studio Build:

Android Studio 4.0
Build #AI-193.6911.18.40.6514223, built on May 20, 2020
Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 5.3.0-61-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 1239M
Cores: 8
Registry: ide.new.welcome.screen.force=true, debugger.watches.in.variables=false
Non-Bundled Plugins: CheckStyle-IDEA, org.jetbrains.kotlin, com.dmarcotte.handlebars

and:

Android Studio 4.2 Canary 2
Build #AI-201.7846.76.42.6582697, built on June 11, 2020
Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 5.3.0-61-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 1927M
Cores: 8
Registry: ide.new.welcome.screen.force=true, debugger.watches.in.variables=false
Non-Bundled Plugins: CheckStyle-IDEA, siosio.kodkod
Current Desktop: ubuntu:GNOME

• Version of Gradle Plugin: 4.0.0 and 4.2.0-alpha02
• Version of Gradle: 6.1.1 and 6.5-rc-1
• OS: Ubuntu 19.10

Steps to Reproduce:

1. Import the attached project
2. Open res/layout/activity_main.xml and notice that it uses <fragment> for the NavHostFragment
3. Open res/navigation/main_nav_graph.xml and see that, under "HOST" in the Destinations section, we have activity_main (nav_host) (see screenshot 1 from Android Studio 4.0)
4. Go back to res/layout/activity_main.xml and accept the quick-fix to switch the <fragment> to a <FragmentContainerView>
5. Go back to res/navigation/main_nav_graph.xml and see that, under "HOST" in the Destinations section, we have "No NavHostFragments found" (see screenshot 2 from Android Studio 4.0)

If we have a warning for <fragment> and a quick-fix to switch to FragmentContainerView, then ideally the navigation editor would honor FragmentContainerView.

Thanks for considering this!