-
Notifications
You must be signed in to change notification settings - Fork 55
Enable Formatic wallet #2388
Enable Formatic wallet #2388
Conversation
|
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.
It works fine for approval, swap and cancellation 👍
(although their message signing UX is not very useful, you have no idea what you are signing)
But the behaviour on page refresh is broken.
Steps:
- Connect with Formatic
- Refresh the page.
- Refresh the page again.
- Upper menu is loaded and you can connect wallet again
- Click on connect wallet and pick Formatic
- It'll connect without needing to login again
Hey @henrypalacios , I have done some tests: sell/buy orders work great! |
@alfetopito the last change will fix the connection on refresh, maybe we could add a loading notification?
|
Sure, if that help UX let's give it a try
👍
I don't think you need to do anything.
Well, yeah, then you'll need to dig into the signing stuff. |
@elena-zh As I mentioned to @alfetopito I have added a notification of connecting when it detects that a provider has connected after refreshing the page. |
@henrypalacios , I was able to test all the rest functionality. However, the issue with cancelling signing I mentioned above is still not fixed. As for 'connecting..' state, it a great idea! The only thing I can mention that in a certain moment of a 'connecting' state connection modal appears, then is closed. Video: https://watch.screencastify.com/v/mlNWW4B6xVeaqNucalPU Thanks |
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.
Yep, working nicely now 👍
The thing still left to address (besides updating the api keys, but that's a follow up PR) is to handle the wallet "rejection"
As mentioned over slack, the Safe handles it, so we can get "inspired" by whatever they did there :)
@elena-zh with the latest change (fortmatic manual update) the rejection wallet should work, what I'm not sure is if everything else is still working, could you test it please? If it works I will go that way. |
Hey @henrypalacios , not I see this error when I try to connect the wallet I cleared all app data storage, but it did not help. |
Now I'm able to connect, but rejection still does not work.. |
@henrypalacios , I retested changes under the current PR, and everything looks good to be besides the cancelling orders' signing issue. I have created a separate issue for this #2413 . |
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.
As discussed, this is already in a working state.
The other 2 points listed below can be addressed in follow up PRs:
- Try to get the signal from the when user closes the signature modal
- Use different API keys for different environments
src/connectors/Fortmatic.ts
Outdated
// TODO implements this | ||
// const pollForOverlayReady = new Promise<void>((resolve) => { | ||
// const interval = setInterval(() => { | ||
// if (provider.overlayReady) { | ||
// clearInterval(interval) | ||
// this.emit(OVERLAY_READY) | ||
// resolve() | ||
// } | ||
// }, 200) | ||
// }) |
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.
What was this for? Do you intend to enable it again or is it no needed for the new version?
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.
That's the point, I checked to see if it is necessary. I did not find that it was necessary after much testing. What I did find is that it is responsible for the strange behavior was commented where the modal reappears:
As it is not part of the custom
I have not removed it, let me know if you think I should remove it.
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.
Ah, good point, I missed it's the original source file!
Then you should mod it instead and do the same thing (comment it out without deleting it)
I have retested the latest changes: LGTM (besides an opened issue #2413 ) |
* testing * Enable Coinbase Wallet (wallet-link) (#2353) * enable walletlink and upgrade package * Limiting the supported networks for CoinbaseWallet * Adding setDefaultInjected provider * Enable Formatic wallet (#2388) * Activate formatic wallet * Adding reconnect Uninjected Provider * Adding connecting web3Status after refresh * Upgrade fortmatic to v2.2.1 * Mute unnecessary Overlay useEffect * Adding new API 🔑 * Adding custom src/custom/connectors/Fortmaitc.ts * merger conflict resolution * set api key according to environment (#2422) * Change clickable, fortmatic supportedChains, enum DefaultInjected * Change CW deeplink * Testing walletLink on mobile
* testing * Enable Coinbase Wallet (wallet-link) (#2353) * enable walletlink and upgrade package * Limiting the supported networks for CoinbaseWallet * Adding setDefaultInjected provider * Enable Formatic wallet (#2388) * Activate formatic wallet * Adding reconnect Uninjected Provider * Adding connecting web3Status after refresh * Upgrade fortmatic to v2.2.1 * Mute unnecessary Overlay useEffect * Adding new API 🔑 * Adding custom src/custom/connectors/Fortmaitc.ts * merger conflict resolution * set api key according to environment (#2422) * Change clickable, fortmatic supportedChains, enum DefaultInjected * Change CW deeplink * Testing walletLink on mobile (cherry picked from commit e88eb5e)
Summary
closes #433
Enable the ability to connect via
Formatic
To Test
Formatic
option.Background
This PR is part of the activation of previously supported wallets #2165