[$250] Android - Profile - Domains and Help buttons remain highlighted after navigating back

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.59-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

1. Open the Expensify app
2. Tap on "Settings" on the bottom of the screen
3. Tap on "Help"
4. Use device back button to navigate back
5. Verify "Help" button is not highlighted anymore
6. Tap on "Domains" button
7. Navigate back with device back button
8. Verify "Domains" button is not highlighted anymore

Expected Result:

"Domains" and "Help" button shouldn´t remain selected after navigating back to app

Actual Result:

After tapping on "Domains" or "Help" buttons and navigating back with device back button, the buttons remain highlighted

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6657941_1731003473938.Domains.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021854637211818328663
• Upwork Job ID: 1854637211818328663
• Last Price Increase: 2024-12-12

Issue Owner

Current Issue Owner: @parasharrajat

[melvin-bot]

Triggered auto assignment to @isabelastisser (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021854637211818328663

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (External)

[truph01]

Edited by proposal-police: This proposal was edited at 2024-11-07 22:21:35 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

After tapping on "Domains" or "Help" buttons and navigating back with device back button, the buttons remain highlighted

What is the root cause of that problem?

• When pressing the "Help" button, the icon fills with green to indicate it’s active. This button navigates the user to an external browser, changing appState.isBackground to true. Upon returning to the app, appState.isForeground is set back to true. However, a logic check here uses a cached image instead of loading a new one:

App/src/components/ImageSVG/index.android.tsx

Line 21 in aedbbde

cachePolicy="memory"

This results in the icon button remaining highlighted after navigating back.

What changes do you think we should make in order to solve the problem?

• We can clear the cache data one the appState.isBackground is true in this:

    const {isBackground} = useAppState();
    useEffect(() => {
        if (isBackground) {
            Image.clearMemoryCache();
        }
    }, [isBackground]);

What alternative solutions did you explore? (Optional)

• We can create a logic using your appState hook to switch the cachePolicy to "none" when the app comes back to the foreground, ensuring it reloads icons and images without caching. Once reloaded, you can set it back to "memory" to use cached images as it is. Here’s a general approach:

    const [cachePolicy, setCachePolicy] = useState('memory');
    const {isForeground} = useAppState();
    const prevIsForeground = usePrevious(isForeground);
    useEffect(() => {
        if (isForeground && !prevIsForeground) {
            // Set cachePolicy to 'none' temporarily when returning to foreground
            setCachePolicy('none');
            // Reset to 'memory' after a slight delay to allow re-render with fresh images
            setTimeout(() => setCachePolicy('memory'), 500);
        }
    }, [isForeground, isForeground]);

• Instead of resetting the cachePolicy to 'memory' by using setTimeout, we can do it in:

App/src/components/ImageSVG/index.android.tsx

Line 18 in aedbbde

<Image

        <Image
            onLoad={() => {
                // Reset to 'memory'
                setCachePolicy('memory');
            }}

[truph01]

Proposal updated

[parasharrajat]

Let see if we get more ideas to solve this issue.

[melvin-bot]

@parasharrajat, @isabelastisser Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[isabelastisser]

Waiting for more proposals.

[parasharrajat]

Yup. waiting for more proposals.

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@parasharrajat, @isabelastisser Eep! 4 days overdue now. Issues have feelings too...

[truph01]

@parasharrajat What do you think about my proposal?

[melvin-bot]

@parasharrajat, @isabelastisser 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[parasharrajat]

No new proposals. @truph01 I will share feedback on your proposal in sometime.

[melvin-bot]

@parasharrajat @isabelastisser this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[parasharrajat]

@truph01 What will happen if we background the app after opening the attachment menu on receipt following steps from this issue #34881. Won't it recreate that issue again with your solution?

[melvin-bot]

@parasharrajat, @isabelastisser Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[truph01]

I will check it today

[melvin-bot]

@parasharrajat, @isabelastisser Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[parasharrajat]

Any update @truph01?

[truph01]

@parasharrajat I am unable to reproduce the bug in #34881 even when I tried to revert the change in PR. So I need more time to test and re-investigate that issue and this one.

[isabelastisser]

@parasharrajat, should we close this?

[melvin-bot]

@parasharrajat @isabelastisser this issue is now 4 weeks old, please consider:

• Finding a contributor to fix the bug
• Closing the issue if BZ has been unable to add the issue to a VIP or Wave project
• If you have any questions, don't hesitate to start a discussion in #expensify-open-source

Thanks!

[melvin-bot]

@parasharrajat, @isabelastisser Whoops! This issue is 2 days overdue. Let's get this updated quick!

[parasharrajat]

I can still reproduce this issue on the latest main. @truph01 Can you try again?

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@parasharrajat, @isabelastisser Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[truph01]

Can you try again

Yes. I can reproduce. I need to investigate the RCA of the issue again

[isabelastisser]

@parasharrajat, please provide an update; thanks!

[parasharrajat]

@isabelastisser No, I can still reproduce this issue.

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[isabelastisser]

Still waiting for proposals.

[melvin-bot]

@parasharrajat, @isabelastisser Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@parasharrajat, @isabelastisser Still overdue 6 days?! Let's take care of this!

[parasharrajat]

Need proposals.