Android应用退出登录后清除ContactItem类数据容器的实现问询

Alright, let's break down how to build this logout flow (clear ContactItem data → navigate to registration screen → load fresh data for new accounts) properly, with code examples and key considerations to avoid data leakage.

1. Core Logout Logic #

When the user triggers logout, you need to completely clear all ContactItem data first, then navigate to the registration screen with a clean task stack (so users can't navigate back to the logged-in state).

Here's a concrete implementation:

// Trigger this method when the user taps the logout button
public void onLogoutButtonClicked() {
    // Step 1: Wipe all ContactItem data from your data container
    clearContactItemStorage();
    
    // Step 2: Navigate to RegistrationActivity and reset the task stack
    Intent registrationIntent = new Intent(this, RegistrationActivity.class);
    // Flags ensure the registration screen becomes the new root of the task stack
    registrationIntent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK);
    startActivity(registrationIntent);
    finish(); // Close the current logged-in screen
}

// Helper method to fully clear ContactItem data
private void clearContactItemStorage() {
    // Adjust this based on how you're storing ContactItem data:
    // Case 1: Global List (e.g., in your Application class or a singleton)
    if (AppGlobalData.contactItems != null) {
        AppGlobalData.contactItems.clear();
    }
    
    // Case 2: Singleton holding a single ContactItem instance
    if (UserContactManager.getInstance() != null) {
        UserContactManager.getInstance().resetContactData(); 
        // Inside resetContactData(), set all fields to default values (null/empty)
    }
    
    // Case 3: Local storage (SharedPreferences/SQLite) - don't forget to clear this too!
    SharedPreferences contactPrefs = getSharedPreferences("contact_storage", MODE_PRIVATE);
    contactPrefs.edit().clear().apply();
}

Why this works: #

• Clearing both in-memory and local storage ensures no leftover data from the old account.
• The intent flags FLAG_ACTIVITY_NEW_TASK | FLAG_ACTIVITY_CLEAR_TASK wipe the existing task stack, so pressing back from the registration screen won't take users back to the logged-in app state.

2. Loading Fresh ContactItem Data for New Accounts #

After a new user registers/logs in, you'll fetch their ContactItem data via your API. Make sure to clear any residual data first (as a safety net) before populating the container with fresh data.

Here's how to integrate your existing API call into this flow:

// Call this method after successful registration/login with the new MSISDN
private void fetchAndLoadContactData(String msisdn) {
    // Double-check: Clear any leftover data before loading new stuff
    clearContactItemStorage();
    
    // Your existing API call, modified to handle data population
    Call<APIResponse<ContactItem>> call = ServicesFactory.getService(this).register(msisdn, getSerialSIM());
    call.enqueue(new Callback<APIResponse<ContactItem>>() {
        @Override
        public void onResponse(Call<APIResponse<ContactItem>> call, Response<APIResponse<ContactItem>> response) {
            if (response.isSuccessful() && response.body() != null && response.body().getData() != null) {
                ContactItem freshContactData = response.body().getData();
                // Populate your ContactItem container with the new data
                populateContactItemStorage(freshContactData);
                
                // Navigate to the main app screen now that data is loaded
                Intent mainIntent = new Intent(RegistrationActivity.this, MainActivity.class);
                startActivity(mainIntent);
            } else {
                // Handle API failure (e.g., show error toast)
                Toast.makeText(RegistrationActivity.this, "Failed to load contact data", Toast.LENGTH_SHORT).show();
            }
        }

        @Override
        public void onFailure(Call<APIResponse<ContactItem>> call, Throwable t) {
            // Handle network errors
            Toast.makeText(RegistrationActivity.this, "Network error. Please try again.", Toast.LENGTH_SHORT).show();
        }
    });
}

// Helper method to populate your ContactItem storage
private void populateContactItemStorage(ContactItem freshData) {
    // Match this to your storage method from clearContactItemStorage():
    // Case 1: Global List
    if (AppGlobalData.contactItems != null) {
        AppGlobalData.contactItems.add(freshData);
        // Or if it's a single item: AppGlobalData.currentContact = freshData;
    }
    
    // Case 2: Singleton
    if (UserContactManager.getInstance() != null) {
        UserContactManager.getInstance().setContactData(freshData);
        // Inside setContactData(), assign all fields from freshData to the singleton's properties
    }
    
    // Case 3: Local storage (if you need to persist data across app restarts)
    SharedPreferences contactPrefs = getSharedPreferences("contact_storage", MODE_PRIVATE);
    SharedPreferences.Editor editor = contactPrefs.edit();
    // Store individual fields of ContactItem (e.g., editor.putString("name", freshData.getName()))
    editor.apply();
}

Key Notes: #

• The extra clearContactItemStorage() call before fetching new data acts as a safety net, in case the logout flow wasn't triggered (e.g., user killed the app instead of logging out).
• Make sure your ContactItem container is accessible across screens (singleton, Application class, or ViewModel) so both logout and login flows can modify the same data source.

3. Additional Considerations #

• If using ViewModel/LiveData to manage ContactItem data for UI, reset the LiveData value in clearContactItemStorage() to ensure the UI updates to show empty/no data after logout.
• For SQLite databases, don't just delete the ContactItem entry—consider wiping the entire table if it's tied to a single user, or add a user ID field to filter data per account.

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