Kotlin实现Activity延迟跳转遇阻，求代码问题排查

Hey there! Let's get that delayed Activity jump working for you. I took a look at your code, and the main issue is that you're trying to run the handler.postDelayed() code directly at the class level—outside of any lifecycle method like onCreate(). That code won't execute correctly because it runs before your Activity is fully initialized, and Kotlin doesn't allow executable code in the class body like that (beyond property initializations).

Here's the Fixed Version Using Handler #

This code moves all the delayed logic into the onCreate() method, where it belongs, and also adds proper Looper handling for newer Android versions:

package com.rearaa.weading
import android.content.Intent
import androidx.appcompat.app.AppCompatActivity
import android.os.Bundle
import android.os.Handler
import android.os.Looper

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)

        // Initialize Handler with main thread Looper (required for API 29+)
        val handler = Handler(Looper.getMainLooper())
        handler.postDelayed({
            // Create intent to navigate to MenuPage
            val intent = Intent(this@MainActivity, MenuPage::class.java)
            startActivity(intent)
            // Optional: Call finish() if you don't want users to return to MainActivity
            finish()
        }, 4000) // Delay in milliseconds (4 seconds)
    }
}

Key Fixes & Explanations: #

• Moved code to onCreate(): This ensures the logic runs after the Activity is properly set up.
• Explicit Looper usage: On Android 10 (API 29) and above, you need to specify the main thread Looper when creating a Handler to avoid runtime exceptions.
• Kotlin Lambda: Using a lambda instead of a separate Runnable makes the code cleaner and more concise.
• Optional finish(): If you add this, users won't be able to go back to the splash screen (MainActivity) using the back button after the jump.

Modern Alternative: Kotlin Coroutines #

If you want to use the more modern Kotlin approach for async tasks, Coroutines are a great option. They make asynchronous code look and behave like synchronous code, which is easier to maintain:

package com.rearaa.weading
import android.content.Intent
import androidx.appcompat.app.AppCompatActivity
import android.os.Bundle
import kotlinx.coroutines.CoroutineScope
import kotlinx.coroutines.Dispatchers
import kotlinx.coroutines.delay
import kotlinx.coroutines.launch

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)

        // Launch a coroutine on the main thread
        CoroutineScope(Dispatchers.Main).launch {
            delay(4000) // Wait 4 seconds
            val intent = Intent(this@MainActivity, MenuPage::class.java)
            startActivity(intent)
            finish()
        }
    }
}

Just note that if your project doesn't already have Coroutines set up, you'll need to add the dependency to your app-level build.gradle file (most new Android Studio projects include this by default):

dependencies {
    implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-android:1.7.3'
}

Either of these solutions will get your 4-second delayed navigation working perfectly!

内容的提问来源于stack exchange，提问作者shirazy