I downloaded the 3.2 Canarius studio and now I want to try to work with the new navigation.

The following tutorial is written in the tutorial.

implementation 'android.arch.navigation:navigation-fragment:1.0.0-alpha02'

I get an error when compiling

Error: Program type already present: android.support.v4.app.INotificationSideChannel

I understand that now if I started using the dependency from the X version, then all dependencies should be of a new format

Found such a link by refactor

https://developer.android.com/topic/libraries/support-library/refactor

but there is nothing about navigation.

The question is how to make the dependency work?

In general, for the time being, it is not entirely clear how the migration to the X version will occur, will it be necessary to find how the dependency will now look for each library that is used in the project?

EDIT

 apply plugin: 'com.android.application' apply plugin: 'kotlin-android' apply plugin: 'kotlin-android-extensions' android { compileSdkVersion 28 defaultConfig { applicationId "com.example.ezplan.navapp" minSdkVersion 23 targetSdkVersion 28 versionCode 1 versionName "1.0" testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner" } buildTypes { release { minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } } } dependencies { implementation fileTree(dir: 'libs', include: ['*.jar']) implementation"org.jetbrains.kotlin:kotlin-stdlib-jre7:$kotlin_version" implementation 'androidx.appcompat:appcompat:1.0.0-alpha3' implementation 'androidx.constraintlayout:constraintlayout:1.1.2' //Navigation implementation 'android.arch.navigation:navigation-fragment:1.0.0-alpha02' implementation 'androidx.lifecycle:lifecycle-extensions:2.0.0-alpha1' testImplementation 'junit:junit:4.12' androidTestImplementation 'androidx.test:runner:1.1.0-alpha3' androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.0- alpha3' }
  • I haven’t climbed into new components yet, but in 3.2 there is such a feature as Jetifier, it refatkorit all your code including libraries and translates all dependency support on androidx - Sviat Volkov
  • one
    on the contrary, I climbed to 3.2) androidX b studio is too raw to develop for them. Spent 3 pm, I decided to return to 3.1 I advise you to wait for the release. - Georgy Chebotaryov
  • @ GeorgyChebotaryov I will most likely do the same - Aleksey Timoshchenko
  • you are using android and not androidx namespace, how do you tie up navigation, which is in alpha c androidx, which is in alpha and of the docks and even in the article you dropped it is not in the list. There are conditions of the gradle and min SDK version, which should be, for * .arch.navigation to work. From myself I can say that everything works and connects, there are internal bugs but you can test it completely. - Shwarz Andrei 2:41 pm
  • Yes, I understand that I use the android dependency, so this is the question of how to convert it into a X dependency. And I linked the article in such a way that it describes how to format the dependencies in the X version. I saw that she was not there and thus wanted to say that even in the docks nothing was said about it. Add a question with your gradator which is not compiled - Aleksey Timoshchenko

0