Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

App Lounge app unable to access google content if signed on with google account.

Summary

My phone is a Samsung Note 10+ (SM-N975F) Just upgraded to /e/os 1.20 (From /e/OS 1.19, using adb) Everything went fine, the phone booted up nicely, seems to work fine.

My only problem is that it seems that App Lounge cannot access google content if logged on with a google account. When I start up app lounge, the icons do not appear normally, flashing grey placeholders are visible for the top 6 sections. Only the Open Source and PWA app icons are visible (and working) normally.

This is how it looks: https://community.e.foundation/uploads/default/original/3X/a/8/a8d6eb81c388f3aa5be377f485962084ee6ee795.gif

In anonymous mode it works most of the time, but sometimes I got a message that it was unable to open an anonymous session at the top of the screen. In this case it does not work in anonymous mode as well. But this does not happen often.

I tried to: -logout from google then sigh back in in app lounge -Delete Storage and Cache in settings/apps (then login to google in app lounge) -switch off all privacy settings on the first screen (tracking, fake geolocation and hide ip address) -remove my google accounts (microG) in system settings and creating it again Nothing seems to work so far.

Components affected App Lounge, application download and install. Paid application download and install.

Priority

I believe the severity level for this should be S2: high, because App Lounge app is critical, it should work fully all the time!

( S1 - critical - mail or nextcloud service fully down S2 - high - some feature not available, like rainloop webmail or onlyoffice S3 - medium - some annoyance like slow loading times, error notifications on the phone, intermitent access… S4 - low - minor problem not preventing the use of the feature, with or without workaround. Eg icons being gone or no image previews )

Has it happened before? It happened when I upgraded from EOS version 1.19 to 1.20

Solutions

Workaround Possible fixes

Not aware of any solution, fix or workaround.

Edited by Tamas Vandorffy