When importing work Manager version '2.7.1', an error occurs that it needs lifecycle version '2.1.0', which cannot be downloaded, but at the same time it is written in the WorkManager documentation that it works with lifecycle version '2.5.1', but when importing lifecycle '2.5.1', another error occurs that WorkManager does not fit this version needs '2.1.0'
If you do not import any version of lifecycle, then this is the error:screen first
If you import but version 2.5.1, then this is:screen onescreen two
screen three
gradle:screen one fourscreen five
I will be grateful if I can find help!
I tried to do invalidate cash and different vpns, I restarted the studio by itself
Related
My gradle build completes successfully, but I get:
WARNING: Unsupported Kotlin plugin version.
The `embedded-kotlin` and `kotlin-dsl` plugins rely on features of Kotlin `1.5.31` that
might work differently than in the requested version `1.6.10`.
All of my build.gradle.kts scripts refer to using version 1.5.31. The only association my project has with version 1.6.10 is that Android Studio has the Kotlin version 1.6.10 plugin added. If I try to disable that plugin, I get a message that several other plugins will be disabled. If I accept that, android studio crashes and will not start up again. It won't start up again even if you reinstall android studio again. The solution is to find the file named "disabled-plugins.txt" and delete that file. It's in your AppData folder and in a JetBrains subdirectory. It turns out that it's one or more of those other disabled plugins that prevents Android Studio from starting up again.
The question I have is how do I fix this version mismatch issue. I can't delete the plugin from Android Studio for the reasons I mentioned above. If I try to update my project to using version 1.6.10 I get literally 100's of unresolved dependencies. And it seems from opinionated investigation that 1.6.10 still have too many issues for general use.
By the way, when I look at the gradle window for the project I can see where the dependencies come from. Usually when I look at the gradle window I just see sub project folders that I can drill into for more information, but for this project, it has an additional folder name dependencies. I don't know how they get into my project. But when I look at their version numbers that's where the 1.6.10 mismatch happens.
So, I think I understand why the warning message is valid, I'm at a lost on what I need to do to correct this situation. For the moment, I'm just ignoring the warning, and so far I'm not finding any issues in proceeding that way. But that's means I'm proceeding, without an understanding of what's going on here! Sometimes that's okay and at other times that's a bad judgment The error message itself seems inverted. I would think that 1.6.10 is the embedded kotlin and kotlin-dsl since it an android studio plugin, but the error message seems to say it in the opposite way. So anyway, if someone can bring some clarity as to what's going on, and how I'm thinking wrongly about this problem would be greatly appreciated.
I'll accept the following as the answer to what's going on about the unsupported kotlin version:
https://github.com/gradle/gradle/issues/13020
So, for the moment, I'll go on like this is just a nuisance warning and ignore that.
What I just did was to re-create my Android Studio from a blank brand new project. I copied and pasted stuff from the previous project into the new project. I copied the source and build.script.kts files, so essentially everything is a copy of the disabandoned project. This new project didn't give me the WARNING message anymore. And in additional, I'm now able to upgrade my project to using kotlin 1.6.10, which I previously couldn't do because of the literally 100's of dependencies resolution issues. Whatever, that issue went away, and a lot of others things started working as expected once I recreated the project. I can't say what got my project into that weird state. Deleting the .gradle and .idea folders, wouldn't fix the problem. I didn't try deleting the JetBrains cache, I wish I would have tried that.
I want to update the coroutines version in my build.gradle file and noticed the latest version of coroutines looks like this (org.jetbrains.kotlinx:kotlinx-coroutines-core:1.3.0-M2). Is it okay to use that as it is or should I use the previous one 1.2.2?
M2 means 2nd Milestone Reached. It should be the build just before Release Candidate and it should be mostly fine but some bugs might still persist.
You can use Version 1.2.2 if you want guaranteed stability
In my app I now have this issue upon building:
The "Xamarin.Build.Download.XamarinBuildAndroidAarProguardConfigs" task could not be loaded from the assembly C:\Users\xxx\Desktop\xxx oud\packages\Xamarin.Build.Download.0.4.6\build\Xamarin.Build.Download.dll. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
I've read in the forum from many users that just restarting Visual Studio would fix this. Other suggested changing the Xamarin.Build.Download package.
Well, just restarting does nothing and changing the package is not possible, because other packages seem to depend on this. So just remove those to? I cannot, because those packages somehow depend on the first package so it just goes back and forth.
All I did yesterday was download the Facebook SDK from NuGet and even though I deinstalled it again, I cannot build - always with the above error.
Suddenly, Android Studio started to prompt that to use the Navigation of Android Jetpack is necessary to install a module android.arch.navigation:navigation-fragment:+.. That is the whole module name.
Two problems. One, I already have it installed, version 1.0.0alpha-06 and second, if I attempt to install it will simply say it could not install.
The main issue here is that five minutes before this happened I DID use the visual editor of this, but it suddenly went like this.
I've already tried to clean the cache, invalidate and restart, but it decided to remain like this. Ideas?
If you are using kotlin then add -ktx for kotlin support
implementation "android.arch.navigation:navigation-fragment-ktx:1.0.0-alpha06"
Consider this dependency too:
implementation "android.arch.navigation:navigation-ui:1.0.0-alpha06"
Another thing: consider using support library with version 27.1.1 or use the 28.0.0
Android Studio v3.0 Canary 4,
but happens for me on Android Studio v2.3.3 too
I'm not sure since when this started to happen, what version or configuration I've made (if any), but I can no longer see libraries/dependencies javadoc:
for instance, RxJava:
Even though, Android SDK does show the javadocs correctly:
This is true for all libs I have, I looked everywhere on the net for this issue, and it seems like I'm the only one.
As a workaround, you can manually specify JavaDoc.
Navigate to jar file, select "Library Properties", click "Specify Documentation URL".
For RxJava 2.x: http://reactivex.io/RxJava/2.x/javadoc/
For RxJava 1.x: http://reactivex.io/RxJava/1.x/javadoc/
Detailed how-to can be found here
It's a bug. Allegedly it was fixed last month, but from what I've seen some extra monkeying is needed to get the correct behavior back - I downloaded the latest Android O artifacts from the SDK Manager, then temporarily changed all build.gradle settings to support Android O, then switched back, and now I see the javadoc again even without supporting O. Here's the bug report: https://issuetracker.google.com/issues/37140074
What you can do as a workaround is to inspect a class in the dependency, and it'll give you the decompiled byte code with an option to "Download...". Click that, source is downloaded, and now you have javadocs. You have to do this for each dependency, but it persists through cleans and resyncs.