There is [at least one] app in the App lounge, for which :
1/ N/A button instead of download
2/ error message coming when selecting N/A button : " Unsupported app ! The app TCL E-ticket is currently unsupported. This is because the app is not yet widely released, or there is some other error "
In this case :
1/ How is it possible to know more precisely about what went wrong ? (does it come from the app developper ? MicroG services ?) (In this particular case, I downloaded Aurora store in my previous -google android- phone and the app was also not there, but only in the app store)
2/ Is it possible that in the future the app will be available ? How can we be informed ? Can we contribute to make the app available ?
My guess is that this is a bug with TCL (or with /e/, idk). You probably cannot see in this image but App Lounge is trying to download edit, actually spending time resolving them (I saw this “resolving” behaviour more clearly later on another search) all TCL apps.
I managed to get the “top” one with my old Samsung A3 (2016)
That’s quite fun that all the tcl apps are trying to download at the same time !
From my side it’s a bit diffrent, the app does not appear, I must look up the tcl site and click on the download button which redirect me to the app lounge.
So it must not come from the app version, as it is the same one for both of us
(!fusedApp.isFree && fusedApp.price.isBlank()) and changed later to (!fusedApp.filterLevel.isUnFiltered())
I think you @luc_pcm run on newer app-lounge code than @aibd - and isUnFiltered() is tripping up on the App. Maybe worth a bugrep if it should not be filtered
my way of thinking in this is - the filter function is doing what it is supposed to do but is overly strict. TCL ticket seems to have paid functions (well, transport tickets), but is not a paid app.
I really haven’t looked into all details of what the Code tries to achieve (isFree / price.isBlank) vs isUnFiltered - maybe you can go in more depth and report back?
This explanation sounds good, because you are wright we can purchase the ticket directly on the app.
I will try to look at the code to precise the report, but I am a basic user, I don’t even know if I will be able to read it .
Is there a documentation or something to start ?
if we detect that the app is not downloadable for a region, we use [UI] level filter
this is what you see with N/A
now I’m unsure if the geo-restriction is enforced by the google-play remote and would otherwise be unexplained to the user why it is failing (so better show N/A) or it has legal reasons to not circumvent them, the MR doesn’t explain the reason, some issue links are internal.
but if the geo-restriction is enforced by the remote (Google Play), the code wouldn’t be able to do something about it but better warn the user. I think the georestriction hinges on the google account that you got assigned from a pool.
I think you could try to log out (in the App Lounge Settings) and relogin (and again possibly) until the app is offered to you?
Perhaps a stupid question but if the issue is that the apps is geo-restricted… Did you have enabled hide-ip function for advanced privacy which coule make you appear in another country?
Your are wright : my position was fake, my ip adresse also, and trackers blocked in app Lounge (default settings)
I’ve all turned to enabled,but the result is still the same
Ok thank you for the tips.
I relog out and signed in one time with my real google account,and with an other randomly attributed and each time it fails ! (And also on aurora store to compare)
I try also tried with my old smartphone [honor 9 lite - android 9] (connection on aurora store with the same google account) this time it works.
As the version is the same (v4.1.1(41)), I guess wether the issue come from a phone setting whether form the android version ?
(config file difference is fine, that’s a profile for the devices screen resolution)
It was easy to debug cleanapk responses, as the api was quite simple and required no auth.
To see the google play server response for the tcl eticket app would maybe explain why it is filtered. I guess the app-lounge developers have something setup for themselves to debug and make sense of a response.
.
