exodus
exodus copied to clipboard
Exodus can't download apps that are only offered for specific devices
When you try to update the analysis for some apps, like taxi.android.client exodus says "report already exists for the downloaded version" which may be true but the scan service doesn't get all version. According to the playstore you can or cannot offer a certain app version depending on the device.
Current Version Varies with device
Therefore the download service should have a fluent identity and mask as different devices with different properties like rooted, vendor, size, android version and so on.
After some offline discussions, it seems this is due to the priority given to the servers downloading the apps, which go in ascending Android API order. Inverting this order could help newer devices, but then it could prevent older versions from being downloaded. It's not trivial to know which version to get without having the Android version, or asking the user to provide a version number. In both cases the interface becomes more complex. Maybe an "expert submission" mode could help with that.
Maybe you could also do an apk upload as expert mode. Rooted devices can carve out the application from the file system . That might also help with scanning apps that people paid for. Those can still include trackers as i noticed recently.
Maybe you could also do an apk upload as expert mode. Rooted devices can carve out the application from the file system . That might also help with scanning apps that people paid for.
We developed a tool for that purpose: https://github.com/Exodus-Privacy/exodus-standalone This is not 100% ideal but it should do the trick. I think anyone who is able to carve out an application from its file system can use exodus-standalone to scan it :).
It probably keeps the results local too which won't benefit other users, will it?
@yoshimo You're exactly right. What I meant is that the possibility to scan these apps exists, although it is not ideal.
This being said, I'm not sure an "apk upload" feature is really something we want to implement because of all the complexity it would imply (note that I'm just talking for myself here).
Although this is the oldest issue, I'll close this one and keep the discussions in #547