You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The google chrome extension shows 0 TON on main net where i have at least 4 TON. Other app on IOS is ok. But i cant swap my coins because the google extension shows zero.
Actual result
When clicked on the google extension, mainnet always shows 0 TON.
Expected result
It should be able to show the mainnet balance accurately
Suggested Severity
Critical
Device
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional Context
No response
The text was updated successfully, but these errors were encountered:
The google chrome extension shows 0 TON on main net where i have at least 4 TON. Other app on IOS is ok. But i cant swap my coins because the google extension shows zero.
Actual result
When clicked on the google extension, mainnet always shows 0 TON.
Expected result
It should be able to show the mainnet balance accurately
Suggested Severity
Critical
Device
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Bug Type
Functional
Reproduction steps
The google chrome extension shows 0 TON on main net where i have at least 4 TON. Other app on IOS is ok. But i cant swap my coins because the google extension shows zero.
Actual result
When clicked on the google extension, mainnet always shows 0 TON.
Expected result
It should be able to show the mainnet balance accurately
Suggested Severity
Critical
Device
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional Context
No response
The text was updated successfully, but these errors were encountered: