Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

643
Views
java.lang.IllegalStateException: SimpleTypeImpl should not be created for error type

Have been facing this error after migrating to AndroidX.

java.lang.IllegalStateException: SimpleTypeImpl should not be created for error type: ErrorScope{Error scope for class <ERROR CLASS> with arguments: org.jetbrains.kotlin.types.IndexedParametersSubstitution@14ac19e7}

This link does not help much

over 4 years ago · Santiago Trujillo
3 answers
Answer question

0

For me, the error was appearing due to invalid import statement. Android Studio didn't show anything regarding the same. I had to go to every single file, then studio shown the invalid import error. Fixed it and the build error's gone.

over 4 years ago · Santiago Trujillo Report

0

I updated to Kotlin 1.3.20 but it still did not work. Then I decided to check the Kotlin source code. I found this link

I had an interface called DisplayItem<T> and I removed its type parameter. After this, I started to get the error. Actually, at the end of the error in logcat it says DisplayItem

So i checked all DisplayItem types in code and I found I forgat to remove one type parameter in a LiveData variable like the follwoing:

MediatorLiveData<DataHolder<List<DisplayItem<MessageViewEntity>>>>

After removing type parameter from the variable it started to compile. I hope this'll help you.

Note: You can use git grep for a quick search.

over 4 years ago · Santiago Trujillo Report

0

My main tip to solve this issue would be when you're just getting the error message with no clue where the real error is, try the Android studio Analyze/Inspect code option. Digging through the output from this I found the actual compile errors that were triggering the problem and then could easily fix them.

The actual problem in my case was when changing a generic class, that had a nested class, into an abstract class and creating two sub-classes to replace it's previous usage. I still had references my code to the original abstract base class where I should have replaced them with one of the two new sub-classes.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!