Complete Guide to Clearing History Stack and Starting New Activity in Android

Problem Background and Requirements Analysis

In Android application development, Activity stack management presents a common challenge. Developers frequently encounter scenarios requiring the clearance of the entire history stack and restarting the application. Specifically, when users perform certain actions in a particular Activity (such as screen C), previous Activities (like screen B) may become invalid, necessitating direct navigation to the initial Activity (screen A) while ensuring it becomes the sole instance in the stack.

Core Solution: Intent Flags

Starting from API level 11, Android introduced specialized Intent flags for this purpose: FLAG_ACTIVITY_CLEAR_TASK. When combined with FLAG_ACTIVITY_NEW_TASK, this flag effectively clears all Activities in the current task stack and launches a new Activity as the root of the stack.

Code Implementation Examples

Implementation in Java:

Intent intent = new Intent(this, ActivityA.class);
intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK);
startActivity(intent);

Equivalent implementation in Kotlin:

val intent = Intent(this, ActivityA::class.java)
intent.flags = Intent.FLAG_ACTIVITY_NEW_TASK or Intent.FLAG_ACTIVITY_CLEAR_TASK
startActivity(intent)

API Compatibility Handling

For devices with API level 10 and below, the IntentCompat class can be used to provide backward compatibility:

// Using support library for compatibility
Intent intent = new Intent(this, ActivityA.class);
intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK | IntentCompat.FLAG_ACTIVITY_CLEAR_TASK);
startActivity(intent);

Technical Principle Deep Analysis

The FLAG_ACTIVITY_CLEAR_TASK flag works by clearing all existing Activity instances associated with the current task. When combined with FLAG_ACTIVITY_NEW_TASK, the system creates a new task stack and designates the specified Activity as the root Activity of that stack. This combination ensures users cannot navigate back to any previous Activities using the back button.

Best Practice Recommendations

In practical development, it's recommended to always check API levels and use appropriate compatibility solutions. For modern applications, setting the minimum API level to 11 or higher allows direct use of native support. For applications requiring support for older versions, integration of Android Support Library or AndroidX libraries is essential for backward compatibility.

Common Pitfalls and Considerations

Developers should avoid using unofficial hack solutions, such as manually calling getParent().finish() or employing other unreliable methods. These approaches not only risk causing null pointer exceptions but may also disrupt the application's normal lifecycle management. The correct approach relies on standard Intent flags provided by the Android framework for stack management functionality.