I’m running into an issue I’ve got a uphold account and I’ve logged in verifying my account on mobile with upholding but the verify button keeps reappearing although I’ve already authorized etc.
you can see verify wallet this keeps popping up everytime
1 Like
anyone gonna help? contacted uphold they said to contact brave forum
MrOwl3
September 9, 2021, 3:25pm
3
Try this. First log in at https://wallet.uphold.com/login then after log in open Brave Rewards at the same tab when you logged in and try to verify wallet. Maybe it will work.
Maybe, you’ve reached the max limit of verified device (4)
1 Like
@Darkside – did what @MrOwl3 suggested work for you?
I’ve only got 3 devices connected to brave/uphold I tried resetting the password to re-authorise that didn’t work either now it’s looping on the login screen, via pc
it did not work I tried that first and it didn’t work I also reset the PW to see if I could re-AUTH but now it’s re-looping on the login screen
Device 1 PC Version Brave:
Version 1.29.79 Chromium: 93.0.4577.63 (Official Build) (64-bit)
](https://brave.com/latest/ )
Device 2 Laptop Version Brave:
Version 1.29.79 Chromium: 93.0.4577.63 (Official Build) (64-bit)
](https://brave.com/latest/ )
Device 3 Mobile Samsung S9+ Version Brave:
Version 1.29.78 Chromium: 93.0.4577.63 (Official Build) (64-bit)
](https://brave.com/latest/ )
fixed the pc login issue but still issues with Mobile
I have the same exact problem.I’ve verified a Windows PC, a Mac mini and I cannot verify my Android phone. I press Verify wallet, Login to Uphold and then I get redirected back to brave rewards and the verify button reappears.
1 Like
Glad to hear that the issue with the desktop version has resolved. On Android I’m now wondering if your Android issue is described here:
opened 03:45PM - 25 Jul 21 UTC
closed 09:37PM - 26 Aug 21 UTC
feature/rewards
QA Pass-Win64
priority/P2
QA/Yes
release-notes/include
OS/Desktop
## Description
If a user gets naturally disconnected (e.g., access token expi… res), the user is sent into the `Disconnected` state (i.e. they see "Disconnected" in the UI, and are not unlinked on the backend). From this state, the user cannot do a hard/explicit disconnect (unlink from backend), because when the user presses the "Disconnected" button, they are immediately sent to the custodian login page.
Some users can end up in an edge case where, for example:
1. They request Uphold to delete their account
2. Their access token expires
3. But they continue to receive deposits to their Uphold account (but these will fail because account no longer exists)
4. Even if they are unlinked on the server, their browser will continue to show them to be "Disconnected"
5. Instead, the user should be able to get back to the fully unverified state and use the browser as fully unverified
## Solution
(1) When user presses "Disconnected" button, it should open the menu:
![image](https://user-images.githubusercontent.com/11497541/126904987-7d3792e5-cba8-4197-acbe-198c0bc7e4a8.png)
It can say "Disconnected" in the top right corner, and be filled in with whichever text makes sense. What's important is that the following options appear:
(2) The options in that menu should be:
1. Log into your {{custodian}} account (where the Disconnect button currently goes directly)
2. Disconnect from Brave Rewards (will call the unlinking endpoint) and return the browser to `unverified` state
Matt I’ve send private msg
@Darkside ,
Why exactly did you send me a DM? The behavior you’re seeing is captured in the issue listed above.
So what do.i need to do to fix it
@Darkside ,
You’ll need to wait for the developers to fix the issue. You can track the progress in the Github link above.
Reading the description of this bug it does not seems at all the problem we are facing
@MuffyOne ,
Is this a more accurate description of what you’re seeing?
opened 05:54PM - 09 Jul 21 UTC
bug
feature/rewards
priority/P2
QA/Yes
OS/Desktop
<!-- Have you searched for similar issues? Before submitting this issue, please … check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
Originally, https://github.com/brave/brave-browser/issues/16410 was supposed to fix https://github.com/brave/brave-browser/issues/16269 which is the original issue that was filed by @Miyayes. However, users are still running into the issue. The current workaround for users is disabling `Shields`. Some more information:
* Seems to be cookie related as enabling `All cookies allowed` via shields fixes the issue
* Allowing the two `Google` cookies that are being blocked also fixes the issue
* Disabling `brave://flags/#brave-ephemeral-storage` via `brave://flags` also resolves the issues
* Logging into Uphold via a new tab before verifying via `brave://rewards` also works
This is what basically occurs when you run into the issue:
* log into Uphold after clicking `Verify` via `brave://rewards`
* you'll get screen mentioning that an email verification is needed
* once you verify via the email, it basically routes you to the login page again
* re-login and you'll get asked to verify yourself via the email again
## Steps to Reproduce
1. launch brave and click on the Rewards icon (run through on-boarding)
2. once rewards has been enabled, go into `brave:/rewards`
3. click on `Verify Wallet` and start running through the login process
4. with some accounts, you'll get asked to verify it's you via an "email verification"
5. click on `Yes, it's me` once you get the email
6. you'll get asked re-enter your credentials again (go through the flow again)
7. you'll get asked to verify yourself via email once again
You'll basically get into a loop where it keeps just sending you verification emails without ever linking your account.
## Actual result:
Users are getting into a loop when required to verify via the email verification flow when attempting to link their wallets
## Expected result:
You should be able to link your Uphold account without getting into a verification loop when required to verify via email.
## Reproduces how often:
100% reproducible with my account but not all accounts are required to verify via an email before logging into Uphold
## Brave version (brave://version info)
```
Brave | 1.28.64 Chromium: 92.0.4515.81 (Official Build) nightly (64-bit)
--- | ---
Revision | dba3af0a9a48954c8b188bc641e651580b7cb7b5-refs/branch-heads/4515@{#1162}
OS | Windows 10 OS Version 2009 (Build 19042.1081)
```
## Version/Channel Information:
- Can you reproduce this issue with the current release? `Yes`
- Can you reproduce this issue with the beta channel? `Yes`
- Can you reproduce this issue with the nightly channel? `Yes`
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? `Yes`
- Does the issue resolve itself when disabling Brave Rewards? `N/A`
- Is the issue reproducible on the latest version of Chrome? `N/A`
## Miscellaneous Information:
CCing @bsclifton @rebron @LaurenWags @szilardszaloki @emerick @pes10k
thought id give an update with a new brave update on my mobile I was able to reauthorise as I got an email but still, any time I click verify it still does the same thing as it did before
I am having this same issue, please tell @Mattches when this problem is resolved
Guessing still not fixed then
system
Closed
October 24, 2021, 12:25pm
20
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.