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
Note: this issue is a bit difficult to reproduce, so you may need to find an innovative way to create the issue and reproduce it.
Issue observed: The banner of Opensea-ethereum network action has already been updated to the new one, however, it still shows the old banner on both iOS and Android platform. We have tried to close the App and reopen it, the issue remains.
On Android, one needs to go to "Settings => App => Capture App => Storage" and clear the cache to recover.
On iOS, one needs to "remove" the app completely in order to clear the cache which is a bad user behaviour.
Expected behaviour: If there is any cache exists, user should be able to see the updated data after re-launch the App.
┆Issue is synchronized with this Asana task by Unito
┆Created By: Tammy Yang
The text was updated successfully, but these errors were encountered:
According to James Chien, the current App uses ion-img, which should be in-memory cache. However, what really happens is different. Need to check as it results in bad user UX.
Note: this issue is a bit difficult to reproduce, so you may need to find an innovative way to create the issue and reproduce it.
Issue observed: The banner of Opensea-ethereum network action has already been updated to the new one, however, it still shows the old banner on both iOS and Android platform. We have tried to close the App and reopen it, the issue remains.
On Android, one needs to go to "Settings => App => Capture App => Storage" and clear the cache to recover.
On iOS, one needs to "remove" the app completely in order to clear the cache which is a bad user behaviour.
Expected behaviour: If there is any cache exists, user should be able to see the updated data after re-launch the App.
┆Issue is synchronized with this Asana task by Unito
┆Created By: Tammy Yang
The text was updated successfully, but these errors were encountered: