Indeed, the Google login is also part of the socials, and the redirect link is managed by the library. We are continuing our investigation on it, and if there are any news or updates, we will let you know.
Regarding your other concern with the Phantom wallet, could you please provide more details on what exactly is happening in your use case? If possible, share a recording showing the issue on your end, mention the device and browser you are using, and if possible, open the browser console to check for any error messages. Also, please ensure your device is updated to the latest OS version.
Every process of elimination has been checked inc OS of the mobiles. Both Android & iOS. Trust and Phantom wallets do not work with the plugin on mobile inc a check through our console and dev flow.
We don’t need to share a recording do we? Surely your devs will check on their own devices too?
It’s been 11 days since first error posted. If our application was reliant on this, there goes the business.
Based on that alone, we have no faith continuing with this plugin or service.
ZQ throw out so many plugins, you can’t fix them when they are bad quick enough.
We have further tested the connetion between wallets you mentioned, and regarding the Trust wallet - it appears to be working fine on our end. For reference, please check this recording: Download 6f8c7b3a-873f-4eec-8061-82936189819f.mp4 | LimeWire
Regarding the Phantom wallet on mobile, we noticed that after connecting, the Phantom app opens but does not give the necessary information back to the bubble. This seems to be related to how the wallet handles third-party connections. We are currently planning to update the plugin’s library to see how the wallet connections will work in that case.
Thank you for your understanding, and we apologize for any inconvenience this may cause. If you have any other questions or run into any issues, please don’t hesitate to reach out.
Yes, we’re constantly working to improve our plugins. In this case, we’ve looked into the prblem and it appears to be related to the library used in the plugin. We are currently waiting for a response from their team so we can further address and resolve the problem with Phantom wallet on mobile devices.
We will keep you updated here when a fix is implemented.
Thanks for your understanding, and if you have any other questions, please let us know.
Hope you are well. I have an issue with the plugin, especially on mobile:
For the connect wallet, i get send to metamask, approve , loads for a very long time back on the website, then i close the window, refresh and log again, this time it works.
When I need to approve USDC, get send to metamask and no window to approve the transactions
One second trial, I was able to log on the first time but then when approving a transaction, I was not sent to metamask.
Thanks for the detailed report — one quick thing we’d like to rule out first is a possible network-related issue, since MetaMask / WalletConnect flows rely on redirects, RPC calls, and deep links that can behave differently depending on the connection.
Could you please test the same page and actions on:
a different Wi-Fi network, and
mobile data, with any VPN / ad blockers disabled
This will help us confirm whether the issue is environmental or coming from the setup itself.
If the behaviour is reproducible across different networks, please send us the relevant screenshots so we can investigate further:
your workflow steps involving the plugin
the plugin element configuration
any errors shown when the issue occurs
Once we have that, we’ll dig deeper and help you pinpoint the root cause.
So trying without any VPN and wifi: Connection flow works, then approving transaction doesn’t, same problem, i get send to the metamask app and then the validation window doesn’t come up.
Trying without any VPN and mobile data: Connection flow works, then approving transaction window doesn’t.
In order to assist you further, could you please provide screenshots of the plugin element configuration as well as the workflow responsible for approving the transaction?
Your video was helpful — it confirms that the API is set up correctly, as we can see successful communication between your app and MetaMask. The fact that only the second workflow consistently fails to run suggests the issue is likely related to either the specific action being used or its configuration.
Once we receive the requested screenshots, we’ll continue investigating and help you move forward.
Thanks for sharing all the details and screenshots — this is very helpful.
Here are some possible causes for this behavior, along with a debugging path to help narrow it down:
Mobile-specific popup issues: Mobile browsers sometimes block MetaMask deeplinks or fail to return correctly after invoking the app. This especially happens when the user isn’t redirected correctly or MetaMask is not brought back to the front.
Missing or incorrectly formatted fields: If gas, gasPrice, from address, or amount are missing or misconfigured, the call may fail silently.
No trigger: The workflow may not be triggering correctly — for example, if the “Only when” condition is not passing or another plugin action is blocking execution.
WalletConnect chain mismatch: You’re using chainId 1 with an Amoy testnet config — but Chain ID 1 is mainnet. Amoy testnet (Polygon) uses chain ID 80002, so this may be causing failures in transaction approval.
Token allowance already exists: In some cases, if a spender already has sufficient allowance, calling approve again won’t trigger MetaMask, as the transaction might be skipped or deemed unnecessary.
Here’s what we suggest testing and confirming next:
Update chainId in the plugin element configuration to match the correct testnet (Amoy = 80002). Using 1 (mainnet) can break things on testnet.
Add a temporary debug alert after the approval action to confirm the action runs. If it doesn’t show, the workflow is likely not triggered.
Try increasing gas value temporarily to see if MetaMask shows the transaction prompt.
Add a console log or Bubble debug step (e.g. “add a breakpoint”) before and after the approve action to make sure the workflow sequence is executing.
Check for browser console errors when you run the action. Errors in the console might reveal if the transaction is rejected or not formed properly.
Try running the same action in a desktop browser with the debug_mode=true enabled to catch any workflow errors.
To help you further, please also share a screenshot of the full workflow that contains the approve action (including triggers and conditions).
Once we receive that, we’ll help you dig deeper and get this resolved!
