Issue: Wallet Connection Persists Across Multiple Telegram Accounts in a Mini App
Description:
When switching between different Telegram accounts within a Mini App, the wallet connection seems to persist across all accounts, leading to unintended behavior. Specifically:
I connect a wallet (e.g., TON Space) using one Telegram account.
After switching to another Telegram account within the same Mini App, the connected wallet from the first account is still visible and accessible.
If I disconnect the wallet on the second Telegram account, the wallet also gets disconnected for the first account, even though it should be independent.
Expected Behavior:
Each Telegram account should have its own independent wallet connection.
Switching to a different Telegram account should prompt for a new wallet connection if one has not already been established for that account.
Disconnecting a wallet on one account should not affect the wallet connection status on another account.
Actual Behavior:
Wallet connections persist across multiple Telegram accounts within the same Mini App session.
Disconnecting a wallet on one account also disconnects it for the second account.
Steps to Reproduce:
Open Telegram Mini App with one Telegram account. (I can reproduce this issue not only in my app but also in Notcoin @notcoin_bot)
Connect a wallet (e.g., TON Space).
Switch to a different Telegram account within the same Mini App.
Observe that the wallet from the first account is still connected.
Disconnect the wallet on the second account.
Switch back to the first account and observe that the wallet is now disconnected.
Environment:
Telegram Mini App
TON Connect SDK (via @tonconnect/ui-react)
Multiple Telegram accounts (same device)
Question:
Is this the expected behavior, or am I missing something in the implementation?
Your Question
Issue: Wallet Connection Persists Across Multiple Telegram Accounts in a Mini App
Description:
When switching between different Telegram accounts within a Mini App, the wallet connection seems to persist across all accounts, leading to unintended behavior. Specifically:
Expected Behavior:
Actual Behavior:
Steps to Reproduce:
Environment:
@tonconnect/ui-react)Question:
Is this the expected behavior, or am I missing something in the implementation?
Context
No response
What have you tried so far?
No response
Relevant Code or Commands
No response
Documentation Check