I have experimented with /e/os a bit and tried to install some apps from App Lounge-Version 2.13.5. It seems that some categories are fast to access while others keep the phone busy forever.
STEPS TO REPRODUCE
(1) Run App Lounge
(2) Enter “Kategorien” to browser categories
(3) Select “Dating” as category.
OBSERVED BEHAVIOUR
(3) Screen is flickering while App Lounge apparently tries to find all apps that can be categorized as a dating app, but otherwise nothing happens. After some time screen turns black.
EXPECTED BEHAVIOUR
(3) App Lounge finds a list of dating apps and shows it on screen, so I can pick an app and install it.
I am on a Samsung Galaxy Note 8 phone using /e/OS latest available update for this phone.
interesting, happens to the “Android Auto” category too.
I guess the playstore has restrictions in place, thus the App gets an empty response and errors out - see NullPointerException: Parameter specified as non-null is null → app can’t hide its disappointment
stacktrace
E undation.e.apps: unhandled exception is caught at thread: DefaultDispatcher-worker-14
E undation.e.apps: java.lang.NullPointerException: Parameter specified as non-null is null: method kotlin.text.StringsKt__StringsKt.isBlank, parameter <this>
E undation.e.apps: at kotlin.text.StringsKt__StringsKt.isBlank(Unknown Source:2)
E undation.e.apps: at foundation.e.apps.ui.applicationlist.ApplicationListViewModel.getException(ApplicationListViewModel.kt:115)
E undation.e.apps: at foundation.e.apps.ui.applicationlist.ApplicationListViewModel.access$getException(ApplicationListViewModel.kt:38)
E undation.e.apps: at foundation.e.apps.ui.applicationlist.ApplicationListViewModel$getList$1.invokeSuspend(ApplicationListViewModel.kt:105)
E undation.e.apps: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
E undation.e.apps: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
E undation.e.apps: at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113)
E undation.e.apps: at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
E undation.e.apps: at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
E undation.e.apps: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:820)
E undation.e.apps: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
E undation.e.apps: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)
E undation.e.apps: Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@6240dc0, Dispatchers.IO]
couldn’t find a bug filed for this - you probably want to get a gitlab account if you already know how to structure a bugreport. You should add the stacktrace then
