loading app throws java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity. [229956001]

Bug

Status Update

No update yet.

Description

EL...@terryberry.com

created issue #1

Apr 21, 2022 06:24PM

Artifact used (ex. androidx.appcompat:appcompat:1.0.0-alpha1): androidx.core:core-splashscreen Version used: 1.0.0-beta02 Theme used: Theme.SplashScreen Devices/Android versions reproduced on: Android 11 Pixel 3a emulator

Relevant code to trigger the issue.

override fun onCreate(savedInstanceState: Bundle?, persistentState: PersistableBundle?) { val splashScreen = installSplashScreen()

  super.onCreate(savedInstanceState, persistentState)

  // simulate something running before loading app...
  runBlocking {
      delay(3000)
  }

  splashScreen.setOnExitAnimationListener { splashScreenView ->
      splashScreenView.remove()
      finish()
      startActivity(Intent(this, SecondActivity::class.java))
  }

}

When I try to debug my app, it crashes with the error "You need to use a Theme.AppCompat theme (or descendant) with this activity."

I follow the migration article exactly (https://developer.android.com/guide/topics/ui/splash-screen/migrate) and it keeps complaining about the theme even though I'm using the correct one, this happens even on a clean application so I'm starting to feel like the library is to blame.

Here is the full stack trace I get from the debug console:

E/AndroidRuntime: FATAL EXCEPTION: main Process: com.demo.splashApiDemo PID: 13601 java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity. at androidx.appcompat.app.AppCompatDelegateImpl.createSubDecor(AppCompatDelegateImpl.java:852) at androidx.appcompat.app.AppCompatDelegateImpl.ensureSubDecor(AppCompatDelegateImpl.java:815) at androidx.appcompat.app.AppCompatDelegateImpl.onPostCreate(AppCompatDelegateImpl.java:536) at androidx.appcompat.app.AppCompatActivity.onPostCreate(AppCompatActivity.java:151) at android.app.Instrumentation.callActivityOnPostCreate(Instrumentation.java:1383) at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3502) at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221) at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201) at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173) at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:223) at android.app.ActivityThread.main(ActivityThread.java:7656) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

If I need to provide any additional information, please let me know.

Comments

EL...@terryberry.com <EL...@terryberry.com> #2Apr 21, 2022 07:00PM

I discovered an interesting path to reproduce. If I remove persistentState from my onCreate method the splashscreen works so apparently it seems using that parameter is the root of the issue.

de...@gmail.com <de...@gmail.com> #3May 6, 2022 12:33PM

I struggled a lot on the same issue, the problem is this new SPLASH API seems to be incompatible with DaggerAppCompatActivity. Calling setOnExitAnimationListener is the culprit.

Message last modified on May 6, 2022 12:51PM

va...@gmail.com <va...@gmail.com> #4Aug 2, 2022 06:49PM

I can see this crash only on Android 12+ and only for Samsung devices, on Google Pixel 6 it's running as expected.

ji...@gmail.com <ji...@gmail.com> #5Nov 10, 2022 02:40PM

same error,use core-splashsreen 1.0.0 with com.google.android.material:material. see https://github.com/material-components/material-components-android/issues/2977

Message last modified on Nov 10, 2022 02:42PM

am...@mirego.com <am...@mirego.com> #6Nov 21, 2022 03:41PM

Did anyone find a fix/workaround for this? We're having the same issue and it's causing multiple crashes

ch...@gmail.com <ch...@gmail.com> #7Jan 30, 2024 12:47PM

Still no fix for this? Having the same issue.

g....@gmail.com <g....@gmail.com> #8Mar 22, 2024 08:47AM

I also have this issue, only happens on a Pixel 6 with Android 14. Tested it with a Pixel 7 and an emulator both with Android 14 and the issue does not occur. This is obviously a blocker from using the "new" Splashscreen API so we'll probably revert it as a consequence until the bug is resolved