Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

StackOverflow Point

StackOverflow Point Navigation

  • Web Stories
  • Badges
  • Tags
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Web Stories
  • Badges
  • Tags
Home/ Questions/Q 245224
Next
Alex Hales
  • 0
Alex HalesTeacher
Asked: August 17, 20222022-08-17T01:37:31+00:00 2022-08-17T01:37:31+00:00In: Android, Kotlin

Upgrading Android kotlin version to 1.5.0 throwing error message on build

  • 0

[ad_1]

My dagger error message looked as follows:

error: [androidprocessor:miscerror]
dagger.android.processor.androidprocessor was unable to process this
class because not all of its dependencies could be resolved. check for
compilation errors or a circular dependency with generated code.

I also had this kapt error: java.lang.reflect.InvocationTargetException (no error message)

I was given which file dagger was not able to properly process, but no exact information on missing dependency. I applied all the fixes I found in this so. I had to carefully examine all the dependencies I could see in the generated by dagger file for which error was shown.

In my case it was dagger not able to find org.jetbrains.annotations.NotNull. I noticed this dependency was upgraded, and due to some fixes I moved to use androidx.annotation.NonNull in my code. I actually didnt depend on org.jetbrains.annotations – it was being included from some other dependency. The error looked as follows:

found in modules jetified-annotations-12.0
(com.intellij:annotations:12.0) and jetified-annotations-16.0.1
(org.jetbrains:annotations:16.0.1)

I was resolving conflicts which ended up so that dependency was not visible by dagger.

As usual in such cases it was very usefull to see dependecy tree and where dependencies are comming from. Some dependencies were outdated and used org.jetbrains:annotations in older version, and I had to either upgrade them or block this dependency from being included in my code with exclude, for example:

implementation ("io.reactivex.rxjava2:rxkotlin:$rxKotlinVersion") {
  exclude group: 'org.jetbrains', module: 'annotations'
}

for dependency tree listing see here: How do I show dependencies tree in Android Studio?

[ad_2]

  • 0 0 Answers
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report
Leave an answer

Leave an answer
Cancel reply

Browse

Sidebar

Ask A Question

Related Questions

  • xcode - Can you build dynamic libraries for iOS and ...

    • 0 Answers
  • bash - How to check if a process id (PID) ...

    • 3 Answers
  • database - Oracle: Changing VARCHAR2 column to CLOB

    • 5 Answers
  • What's the difference between HEAD, working tree and index, in ...

    • 4 Answers
  • Amazon EC2 Free tier - how many instances can I ...

    • 0 Answers

Stats

  • Questions : 43k

Subscribe

Login

Forgot Password?

Footer

Follow

© 2022 Stackoverflow Point. All Rights Reserved.

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.