Fix: Card browser list contents not shown just after language change

[Siddheshjondhale]

Purpose / Description

Fixes the issue where the card browser list contents were not shown just after a language change. The fix ensures the columns and data are properly reinitialized and displayed after the language is switched.

Fixes

• Fixes Card browser list contents are not shown just after language change #17803

Approach

This change reinitializes the browser columns using a lifecycleScope to ensure proper display of list content when returning to the screen after a language change.

How Has This Been Tested?

The issue was tested by switching between different languages and verifying that the card browser's list contents.
Physical Device (Samsung Galaxy A6+)

Screen_Recording_20250116-025053_AnkiDroid.1.1.mp4

Checklist

Please, go through these checks before submitting the PR.

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[BrayanDSO]

I feel that this isn't the ideal fix. It adds a lot of extra computation every time that the activity calls onResume, which is relatively frequent, and 99% of the times it will be wasted, since changing languages isn't frequent + it is fixable by closing/reopening the browser + the language need to be changed while the browser is in the backstack

I guess that it is a problem with the activity initialization, or with how the backend is reset after changing a language. Only way to tell is to actually investigate and try to solve it

@david-allison will definitely have a better guess than me here.

[Siddheshjondhale]

I feel that this isn't the ideal fix. It adds a lot of extra computation every time that the activity calls onResume, which is relatively frequent, and 99% of the times it will be wasted, since changing languages isn't frequent + it is fixable by closing/reopening the browser + the language need to be changed while the browser is in the backstack

I guess that it is a problem with the activity initialization, or with how the backend is reset after changing a language. Only way to tell is to actually investigate and try to solve it

@david-allison will definitely have a better guess than me here.

That makes sense.

One approach came to my mind and I tested moving the lifecycleScope block into onCreate() and it works fine. Since onCreate() gets called again after a language change, it reinitializes the columns only when needed, which avoids the extra computation in onResume()

@david-allison @BrayanDSO let me know what you think

[david-allison]

See 1a8fb3e