search

Sifchain / sifchain-ui

Sifchain UI
sifchain-ui.vercel.app
Other
18 stars 20 forks source link

Balances - Some of name of the coin changes to NANOLIKE while scrolling and balances are disappear #727

Open applause-sifchain opened 2 years ago

applause-sifchain commented 2 years ago

View your issue at Applause Testing Services - https://platform.applause.com/products/27939/testcycles/376742/issues/5695554 ---- ACTION DETAILS ----

Action Performed:

  1. Access test url: https://devnet.sifchain.finance/?_env=testnet and make sure connected to Sifchain Keplr
  2. Click Balances
  3. Click "Show all available"
  4. Scroll down while the coins are loading
  5. Almost all coins were replaced by NANOLIKE
  6. Keep scrolling up and down

Expected Result: The balances of the available coins are still visible and the name of the coins should not be replaced by NANOLIKE

Actual Result: The balances of the available coins are no longer visible and the name of the coins were replaced by NANOLIKE

Additional Info:

Error Code/Message: Please import assets to view balances

---- Applause Team Lead Recommendation ----

From Reggie Baraza Reproducible: Unsure In scope: Yes Not a duplicate: yes Seems valid: yes Suggested value: somewhat valuable Comment:

---- ENVIRONMENT ----

Language:English,Operating System:Windows,Web Browser:Chrome,Desktop Accessories:Webcam,Desktop Accessories:Microphone,Desktop Accessories:Speakers,Desktop Accessories:Headset,Operating System Version:10 64-bit,Antivirus:Windows Defender,Operating System Major Version:Windows 10

---- APPLAUSE PROPERTIES ----

Applause Issue/Bug ID: 5695554

Title: Balances - Some of name of the coin changes to NANOLIKE while scrolling and balances are disappear Status: Approved

Type: Functional Frequency: Every Time Severity: Medium

Product (Build): Sifchain (Web) (Dev.net) Test Cycle: Sifchain - Cryptocurrency Wallet and Token - Test Case Cycle - 08/18/2022

---- APPLAUSE ATTACHMENT(S) ----

Bug5695554_Issue01.mp4 : https://utest-dl.s3.amazonaws.com/13094/27939/376742/5695554/bugAttachment/Bug5695554_Issue01.mp4?AWSAccessKeyId=AKIAJ2UIWMJ2OMC3UCQQ&Expires=1976767949&Signature=q9rFAap4ZZ%2FvBuPPQ7udSo4JVao%3D

Bug5695554_Issue01.mp4

alanrsoares commented 2 years ago

@sheokapr this is an envrionement specific issue, not a regression in any form. The behaviour is observed when the token registry of token configs specific to the environment may have duplicated keys. It's not something that would be reproducible in production.