[Android] Rewards buttons to link custodians are not functioning when engaged with, and BAT icon in url bar not responsive

[lukemulks]

Description

When I attempt to link my Gemini account to Brave://Rewards on Android, both custodial account buttons are not functioning correctly.
The buttons are responsive when tapped, but do not navigate to the custodial partner to link the account when engaged with.

Steps to reproduce

1. On Android, go to brave://rewards
2. Click to connect custodial account on either option.
3. Buttons respond, but do not navigate to custodial partner to link account.

For bat icon being unresponsive in url bar, try tapping on the icon.

Actual result

Video of bat icon in url bar being unresponsive:

2023_03_29_20_55_41.mp4

Video of custodial account buttons not navigating to partner sites when engaged with:

2023_03_29_20_57_12.mp4

Note: I am on a Samsung Fold3 phone, and have attempted this for both items above in folded and unfolded mode, and am encountering the same issue from both screen modes.

Expected result

buttons should work

Issue reproduces how often

Version/Channel Information:

tbd

• Can you reproduce this issue with the current Play Store version? Yes v1.49.429
• Can you reproduce this issue with the current Play Store Beta version? Tbd
• Can you reproduce this issue with the current Play Store Nightly version? Tbd

Device details

• Install type (ARM, x86):
• Device type (Phone, Tablet, Phablet): Samsung Fold3
• Android version:

Brave version

1.49.429

Website problems only

• Does the issue resolve itself when disabling Brave Shields? Na
• Does the issue resolve itself when disabling Brave Rewards? Na
• Is the issue reproducible on the latest version of Chrome? Na

Additional information

Cc: @Miyayes and @anthonypkeane - I am hoping my case is an anomaly, but we should look into this as a priority because this breaks the ability to earn BAT.

[Miyayes]

@deeppandya Possibly related to #21057? @lukemulks will help confirm with his brave://rewards-internals while this issue is actively occurring.

[Miyayes]

Continuing to assume it is #21057. Workaround for now is an app restart. We also merged in some code that might make mitigate this issue and make it less likely.