[Hilt] Incorrect signature attribute?

[mrjameshamilton]

Given an Application class with a generic superclass, Hilt inserts the Hilt_ application class into the hierarchy but the signature attribute annotation is not updated with the new superclass. Is this intended behaviour or a bug?

Example:

open class BaseApplication<T> : Application()

@HiltAndroidApp
class MyApplication : BaseApplication<String>() {
    override fun onCreate() {
        super.onCreate()

        println(this.javaClass.superclass)
        println(this.javaClass.genericSuperclass)
        println(this.javaClass.genericSuperclass.typeName)
    }
}

Without Hilt:

.class public final Lcom/example/hiltexample/MyApplication;
.super Lcom/example/hiltexample/BaseApplication;

# annotations
.annotation system Ldalvik/annotation/Signature;
    value = {
        "Lcom/example/hiltexample/BaseApplication<",
        "Ljava/lang/String;",
        ">;"
    }
.end annotation

class com.example.hiltexample.BaseApplication
com.example.hiltexample.BaseApplication<java.lang.String>
com.example.hiltexample.BaseApplication<java.lang.String>

With Hilt the superclass in the signature attribute doesn't change and therefore doesn't match the actual superclass anymore:

.class public final Lcom/example/hiltexample/MyApplication;
.super Lcom/example/hiltexample/Hilt_MyApplication;

# annotations
.annotation system Ldalvik/annotation/Signature;
    value = {
        "Lcom/example/hiltexample/BaseApplication<",
        "Ljava/lang/String;",
        ">;"
    }
.end annotation

class com.example.hiltexample.Hilt_MyApplication
com.example.hiltexample.BaseApplication<java.lang.String>
com.example.hiltexample.BaseApplication<java.lang.String>