IssueTracker

I recently noticed that after a fresh app install for a project that targets api 33, the launcher activity goes through an onCreate/onDestroy flow then it is created again.

I have the following setup:

app build.gradle: compileSdk 33, minSdk 24, targetSdk 33

compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
    kotlinOptions {
        jvmTarget = '1.8'
    }

root build.gradle

plugins {
    id 'com.android.application' version '7.4.0' apply false
    id 'com.android.library' version '7.4.0' apply false
    id 'org.jetbrains.kotlin.android' version '1.7.21' apply false
}

AndroidManifest activity declaration:

<activity
            android:name=".MainActivity"
            android:exported="true">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />

                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
</activity>

MainActivity Code:

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        Log.d("MY_LOGS", "onCreate")
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)
    }

    override fun onResume() {
        Log.d("MY_LOGS", "onResume")
        super.onResume()
    }

    override fun onPause() {
        Log.d("MY_LOGS", "onPause")
        super.onPause()
    }

    override fun onDestroy() {
        Log.d("MY_LOGS", "onDestroy")
        super.onDestroy()
    }
}

Logs output on fresh start-up after app install:

2023-06-29 17:23:54.548 24822-24822 MY_LOGS                 com.example.teststartup2             D  onCreate
2023-06-29 17:23:54.649 24822-24822 MY_LOGS                 com.example.teststartup2             D  onResume
2023-06-29 17:23:54.992 24822-24822 MY_LOGS                 com.example.teststartup2             D  onPause
2023-06-29 17:23:54.994 24822-24822 MY_LOGS                 com.example.teststartup2             D  onDestroy
2023-06-29 17:23:55.021 24822-24822 MY_LOGS                 com.example.teststartup2             D  onCreate
2023-06-29 17:23:55.042 24822-24822 MY_LOGS                 com.example.teststartup2             D  onResume

Device used: Samsung Galaxy S22 Ultra, Android 13, One UI Version (if it matters) 5.1

Has anyone else encountered this? Is it normal for this to occur? This can cause problems if one relies on the fact that the Launcher activity should be started (onCreate lifecycle flow) only once on fresh app startup.