-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: Reject the sign request when cancelling the authentication method + fix cookies issue #16091
Conversation
… for each account WalletConnect cannot operate on shared cookies in between accounts. This commit will split the cookies and cache in different folders with the user public key as folder name.
TODO: Analyse recovery options
@virginiabalducci This PR should also fix the shared cookies issue! |
Jenkins Builds
|
@caybro @Khushboo-dev-cpp This one is failing again 🙈
|
@@ -114,6 +114,7 @@ SQUtils.QObject { | |||
if (session === null) | |||
return | |||
root.displayToastMessage(qsTr("Failed to authenticate %1 from %2").arg(methodStr).arg(session.peer.metadata.url), true) | |||
root.sessionRequestResult(request, false /*isSuccessful*/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alexjba this is nice, but can we do the same if the user cancels the "Sign" request? That happens before the authentication popup is run.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do. We reject any sign request if the sign modal is closed in any other way except when hitting Sign
Yeah, this one tends to fail from time to time, I'll look into that. But I was never able to reproduce it locally, it's just on CI :/ |
Ive noticed too! def needs to be looked at... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested this with different accounts and looks good on my end!
What does the PR do
closes #16088
+Fixing the shared cookies issues on WalletConnect
Affected areas
WalletConnect
Architecture compliance
My PR is consistent with this document: Architecture guidelines
Screenshot of functionality (including design for comparison)
Impact on end user
What is the impact of these changes on the end user (before/after behaviour)
The dApp flow is completed even when the authentication fails.
Each user profile will use its own cookies for WC
How to test
Risk
Described potential risks and worst case scenarios.
Tick one: