You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Navigation 1.0.0-alpha06 is out now with support for Shared Element Transitions for both activities and fragments (plus an Extras API for passing anything to custom Navigators):https://developer.android.com/jetpack/docs/release-notes#september_20_2018 …
Javadoc for the new Navigation classes is coming shortly, but you can see what the Shared Element Transition APIs look like in the updated docs:https://developer.android.com/topic/libraries/architecture/navigation/navigation-implementing#shared-element …
Hey @ianhlake. Do you know when you're going to update the dependency to "androidx.navigation.*" instead of "android.arch.navigation.*"?
Don't get it... sorry... 
both are enable in my http://gradle.properties
android.enableJetifier=true
android.useAndroidX=true
I'm using Android Studio 3.2 with gradle plugin 3.2.0.
Then if that isn't working for you, you should file a bug against the AndroidX team with a project that replicates your issue: https://issuetracker.google.com/issues/new?component=192731 …
Yeah, sorry, I must have explained myself poorly. android.arch.navigation is what you need and should work in both AndroidX and non-AndroidX apps - Jetifier does all the work to convert *every* library into AndroidX for you so there's no androidx.navigation needed.
Gotcha! But, why only this package is not using the androidx.* dependency pattern? Is there any plans to migrate?
You can't use androidx.* dependencies in non-AndroidX projects (Jetifier only works non-AndroidX to AndroidX, not the reverse) so cutting off anyone not yet moved over to AndroidX seems like a bad move. Like I said earlier, we'll be providing an androidx version later.
There is a typo on the documentation. Shouldn't it be FragmentNavigator.Extras?pic.twitter.com/SvfJfcjFKc
Nope, that's the navigation-fragment-ktx extension that bypasses the Builder structure of FragmentNavigator.Extras
Ooooohhh, thanks, I wasn't expecting this! I've been using navigation library all this time without the "ktx" version 
. Learned a new thing today.
Yep, we mention the ktx modules on the Adding Components page: https://developer.android.com/topic/libraries/architecture/adding-components#navigation … but it is easy to miss. Enjoy! :-)
Any plan to add "http://transaction.show (fragment)" or "hide" instead of "add/pop"?
No, but I'd love to hear what your use case is.
A lot, i dont want to recreate the fragment i have created before. For example, bottom navigation fragments. Once i open e.g. second menu item, then third and come back to second fragment again, i dont want to recreate it again (save/restore states). Instead just add/show/hide.
Great, that gives a lot more context. We're looking at bottom nav specifically in https://issuetracker.google.com/issues/80029773 so that'll be the best place to get updates and I'll keep this in mind.
Thank you for update. IMO, absence of tools to support multiple fragments stacks (and display these stacks in the preview) is definately one of the most important issues which impede usage of this great lib widely in production.
You mean Instagram like bottom nav. right? Each menu item has its own stack of screens.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
