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

Question

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

Make sure you updated all: IDE, Gradle, Kotlin version, Kotlin IDE plugin etc. I believe I had this once and it was IDE/plugin related. — shkschneider, Jan 14 '19 at 15:24
@UtkarshBarsaiyan I had to make changes manually even after choosing Migrate to AndroidX from Android Studio and I have realised until everything is up to date(versions, IDE, gradle, code etc), this error wont go. — Shahzeb, Jan 16 '19 at 02:21
I found that the next line after the `java.lang.IllegalStateException` line gives you the name of the problematic class. In my case, I didn't have the gradle dependency (for rxjava) in the offending library module. — AgileNinja, Feb 15 '19 at 20:57
In addition to @AgileNinja's suggestion, my error was outputting `[ERROR: Response]`. It was because I had removed the retrofit dependency from one of my modules. Nice 2 hours wasted... — StuStirling, Jun 11 '19 at 13:22

score 37 · Accepted Answer · answered Apr 05 '19 at 04:44

37

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.

answered Apr 05 '19 at 04:44

theapache64

10,926
9
65
108

It actually showed in the preview of each file when searching for "import", which gave me more clues of what had gone wrong. – Rickard Elimää Aug 26 '19 at 12:54
3

It is indeed the missing imports are the caused on my side. Use the *Analyze > Inspect Code* menu if you don't want to go every single file checking the missing imports. – glagarto Dec 18 '19 at 20:01
1

For me, it was a similar problem. Also, the import was in a test file, which I've observed in the past that don't get a compiler check by the IDE until they are run or opened... – pablisco Aug 01 '20 at 16:51
1

Similar problem. Thank you for your experiences. – Georgiy Chebotarev Aug 03 '20 at 14:18
@pablisco you saved my day. My missing import statement was indeed located in a test file – Cris Aug 05 '20 at 11:57

savepopulation · Answer 2 · 2020-09-07T12:50:32.733

18

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.

edited Sep 07 '20 at 12:50

answered Feb 12 '19 at 08:51

savepopulation

11,736
4
55
80

1

I have many classes in which I use `` and I cannot remove them as it is needed. Is there any other solution? – Malwinder Singh Feb 25 '19 at 07:22
2

`git grep` on what? – IgorGanapolsky Oct 21 '19 at 18:47
when you check the logs it says the type. you should grep the type and check in which one you missed to remove the type parameter. – savepopulation Oct 22 '19 at 07:12
1

@IgorGanapolsky In my case the problematic broken class was `Event' *` and I found a ViewModel with a wrong import. Godspeed, my friend. – Ivan Morgillo Jul 10 '20 at 08:31
This may be late. But search for LiveData in my case I found that some templates were referring to non existent types – user210504 Aug 11 '20 at 21:51

score 9 · Answer 3 · answered Jun 06 '19 at 09:41

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.

score 4 · Answer 4 · answered Feb 25 '19 at 07:29

Migrate to AndroidX option in Android Studio didn't help much. I solved this error by making changes in every file manually, changed the package names according to AndroidX in both code and xml. If any file is left unchanged, you will see this error. Please make sure your Kotlin plugin version, gradle plugin version, build tools and Android studio version is up to date.

score 4 · Answer 5 · answered Jun 03 '21 at 16:00

I did following steps to solve the issue.

1-Updated android studio from 4.1.1 to 4.2.1

2-Update below line in gradle-warepper.properties file

distributionUrl=https\://services.gradle.org/distributions/gradle-6.9-all.zip

3- Update some kotlin extentions like below

buildscript {
    ext.kotlin_version = '1.3.72'

to

buildscript {
    ext.kotlin_version = '1.4.32'

 dependencies {
        classpath 'com.android.tools.build:gradle:4.0.1'

to

dependencies {
        classpath 'com.android.tools.build:gradle:4.2.1'

It will take some time for gradle sync etc but finnaly for me solved the problem after waisting whole day.

score 3 · Answer 6 · answered Jan 20 '22 at 07:08

3

I just updated my kotlin-gradle-plugin version in root build.gradle and it resolved my issue

classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.72"

to

classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.4.32"

answered Jan 20 '22 at 07:08

Nihas Nizar

619
8
15

Probably an outdated version of kotlin plugin... – IgorGanapolsky Feb 26 '23 at 12:03

score 1 · Answer 7 · edited Feb 27 '23 at 01:13

1

Upgrade your Kotlin dependency to 1.7.20 and the compiler will highlight the source of your issues.

edited Feb 27 '23 at 01:13

IgorGanapolsky

26,189
23
116
147

answered Jan 24 '19 at 14:07

kassim

3,880
3
26
27

Seems like an old version of Kotlin... – IgorGanapolsky Feb 26 '23 at 12:05
1

yep, post was from Jan 2019 – kassim Feb 26 '23 at 23:35

score 1 · Answer 8 · answered Nov 08 '22 at 09:28

1

If this error is related to import. So we can also do this

Right click on module -> Optimise Imports.

In this way we can save time from going to every single file and findout that import.

answered Nov 08 '22 at 09:28

Fahd Tahir

55
5

This definitely saves time from going to every file, and displays meaningful compiler errors. – IgorGanapolsky Feb 26 '23 at 12:06

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

8 Answers8

Linked