search

status-im / status-desktop

Status Desktop client made in Nim & QML
https://status.app
Mozilla Public License 2.0
287 stars 78 forks source link

STATUS_RUNTIME_TEST_MODE = 'True' (keycard mock window) leads to UI loading with delay #15504

Closed anastasiyaig closed 3 weeks ago

anastasiyaig commented 1 month ago

Bug Report

Description

image

app_20240709_163035.log aut (1).log

Similar issue happens to Community portal screen

image

Steps to reproduce

  1. export STATUS_RUNTIME_TEST_MODE = 'True'
  2. run the app and create new account
  3. notice that there are 2 windows running now, keycard mock and status app windows
  4. go to settings -> wallet
  5. notice a visible delay when loading the wallet settings screen

It is very visible with autotests. Also, it is not the case when i dont have this env var set.

Some suspects:

WRN 2024-07-09 16:30:52.076+03:00 qt warning                                 topics="qt" tid=18251 text="TypeError: Cannot call method 'resetStack' of null" file=qrc:/app/AppLayouts/Profile/ProfileLayout.qml:130 category=default

Could be related to having 2 Qt windows opened as well. The monitoring flag opens the monitoring window. The testmode flag opens the keycard window.

per @micieslak it depends if async loading is on or off and it's a bug in the component

Expected behavior

async loading flag shouldn't change based on testMode flag

Actual behavior

component is sensitive to initialization order internally which is undefined

Additional Information

anastasiyaig commented 1 month ago

@alexjba @caybro

anastasiyaig commented 1 month ago

UPD: thanks to @IvanBelyakoff , in https://github.com/status-im/status-desktop/pull/15540 i confirmed, that application behaves normally (much better anyway) under STATUS_RUNTIME_TEST_MODE = True when keycard mock controller window is not showing up.

So it could be assumed indeed that the issue is with having 2 qt windows

anastasiyaig commented 3 weeks ago

@caybro was it closed by mistake?