App Lounge - apps installation with difficulties in A13/T
- /e/ version: e-1.14-rc-T-dev
- Device model(s): Beryllium
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: yes
Summary
I recently installed A13/T. The system is working pretty stable. I only discovered an unusual behavior with App Lounge v.2.5.9 that can be described as follows:
- Various but not all search queries within App Lounge terminate with a "Timeout fetching applications!"
- This behavior is a regression compared to AL v.2.5.7 (e-1.13)
The problem
Steps to reproduce
- Fresh install of install of e-1.14-rc-T (not tested yet whether the behavior can be reproduced with other versions than A13/T)
- Open App Lounge
- Search for "skype" or "tagesschau"
- Make sure between different search queries to fully close App Lounge.
What is the current behavior?
When the user searches for "skype" or "tagesschau", a list of available apps is being shown (including the ones the users is likely to install), but the App seems to continue searching (there is a new activity indicator above the 5 function keys). With the 2 queries above the activities bar keeps on moving for about 20-30 seconds until an error message "Timeout fetching applications!" is appearing (see PIC-1). In between the user could opt to install one of the shown apps. This is being executed correctly, the error message is appearing then anyway.
As soon as the user searches for a term where the activity indicator does not keep on rolling (example: "whatsapp"), the error message is not popping up
The behavior is not always consistent. Sometimes (always trying out the same 2 queries "skype" or "tagesschau") a list of apps is not being shown at all but it seems the app continues searching. In this case the error message pops up after 20-30 sec. (see PIC-2). This latter behavior I was able to reproduce last week, but not anymore today
When the user searches for an app a list should be shown and an app should be installed without a timeout error.
Technical information
Relevant logs (adb logcat)
Relevant screenshots
Solutions
Workaround
Possible fixes