Introduction

The crash message You need to use a Theme.AppCompat theme (or descendant) with this activity means an AppCompatActivity started with a theme that AppCompat cannot work with. In practice, the activity class, the manifest theme, and the style parent are out of sync.

The fix is usually simple once you check those three pieces together. Most cases come down to using a platform android:Theme.* theme with AppCompatActivity, or mixing old support-library assumptions with AndroidX code.

Why the Crash Happens

AppCompatActivity expects an AppCompat-compatible theme. That can be:

• 'Theme.AppCompat.*'
• or a compatible descendant such as many Material Components themes built on AppCompat

This mismatch is enough to crash:

• activity extends AppCompatActivity
• active theme inherits from android:Theme.*

AppCompat initializes theme attributes very early. If those attributes are missing, startup fails before the screen can render.

Define a Compatible Theme

In your theme resources, inherit from an AppCompat or compatible Material parent:

1<resources>
2    <style name="Theme.MyApp" parent="Theme.AppCompat.Light.NoActionBar">
3        <item name="colorPrimary">#1565C0</item>
4        <item name="colorPrimaryDark">#0D47A1</item>
5        <item name="colorAccent">#FF6F00</item>
6    </style>
7</resources>

Or, for a Material Components theme:

1<style name="Theme.MyApp" parent="Theme.MaterialComponents.DayNight.NoActionBar">
2    <item name="colorPrimary">#00695C</item>
3    <item name="colorSecondary">#F9A825</item>
4</style>

The important part is the parent theme, not the specific color values.

Apply the Theme in the Manifest

Make sure the manifest actually uses that theme:

1<application
2    android:name=".MyApplication"
3    android:theme="@style/Theme.MyApp">
4
5    <activity android:name=".MainActivity" />
6</application>

Or on one specific activity:

<activity
    android:name=".SettingsActivity"
    android:theme="@style/Theme.MyApp" />

It is common to define the right theme in XML but forget to apply it in the manifest, which leaves the crash unchanged.

Keep the Activity Base Class Consistent

The activity should match the theme family:

import androidx.appcompat.app.AppCompatActivity

class MainActivity : AppCompatActivity(R.layout.activity_main)

If you intentionally want to use a pure platform Activity with platform themes, then do not use AppCompat widgets and do not extend AppCompatActivity. The theme and base class must belong to the same UI stack.

Check Dependencies and Runtime Overrides

If the theme looks correct but the crash persists, inspect a few less obvious causes:

• old support libraries mixed with AndroidX
• flavor-specific theme overrides
• 'values-night themes using a different incompatible parent'
• runtime setTheme(...) calls applying the wrong style

These cases are less common than a plain wrong parent theme, but they do happen in larger apps.

It also helps to confirm that the project is consistently using AndroidX AppCompat and not an accidental mix of old support artifacts. Theme crashes sometimes look like style mistakes when the real issue is a dependency set that resolves incompatible resources.

Common Pitfalls

The biggest mistake is using a platform theme such as android:Theme.Light with AppCompatActivity. That combination is not supported.

Another common issue is defining the correct theme but never applying it in the manifest, so the app still launches with the old one.

Developers also sometimes fix only the main theme while a flavor, test manifest, or night-mode theme still points to an incompatible parent.

Finally, watch for mixed dependency stacks. Old support-library artifacts and AndroidX AppCompat code do not belong in the same modern project setup.

It is also worth checking for runtime theme overrides. A late setTheme(...) call with a platform theme can recreate the same crash even if the manifest theme looks correct on disk.

Summary

• This crash happens when AppCompatActivity runs under a non-AppCompat-compatible theme.
• Inherit your theme from Theme.AppCompat.* or a compatible Material descendant.
• Apply that theme in the manifest or activity declaration.
• Keep the activity base class and theme family aligned.
• If the crash persists, inspect flavor overrides, night themes, and runtime setTheme(...) calls.