Status Update
Comments
dl...@gmail.com <dl...@gmail.com> #2
dl...@gmail.com <dl...@gmail.com> #3
ja...@google.com <ja...@google.com>
ja...@google.com <ja...@google.com> #4
- Unable to access your files due to file restrictions.
Note: Please upload to google drive and share the folder to
lb...@gmail.com <lb...@gmail.com> #5
ja...@google.com <ja...@google.com> #6
Note: Please upload to google drive and share the folder to
- Attachments in
have been set to "Restricted Access."comment #1
lb...@gmail.com <lb...@gmail.com> #7
lb...@gmail.com <lb...@gmail.com> #8
But please stop changing access to yourself. I can't hold all the files I upload here.
And you don't have auto-deletion on Google Drive for some reason.
ja...@google.com <ja...@google.com> #9
lb...@gmail.com <lb...@gmail.com> #10
I tried now again.
lb...@gmail.com <lb...@gmail.com> #11
ja...@google.com <ja...@google.com> #12
In review:
- With API 30, I was able to get a list of apps with APEX and they were set to true.
// API 30
2020-10-05 11:58:58.813 14443-14508/com.lb.myapplication D/AppLog: com.google.android.vndk.v30 isApex?true
2020-10-05 11:58:58.813 14443-14508/com.lb.myapplication D/AppLog: com.google.android.media isApex?true
- With API 29 I was able to get similar results as compared with your provided screen shot
// API 29
2020-10-05 12:02:32.754 25515-25597/com.lb.myapplication D/AppLog: apexApps:209 allApps:209
note: from the screen shot you provided it does also seem you are viewing the logs from a device using API 29.
To confirm: the issue is that you are not able to get information on which apps are APEX or not while using API 29, correct?
lb...@gmail.com <lb...@gmail.com> #13
Odd.
Was sure I tested on API 30 too. Sorry for that. Perhaps I did the wrong filtering, temporarily.
So for some reason I failed for API 29.
On API 30 though, I can see there are more items for the `apexApps` variable than the `allApps` for some reason.
Also, I was told (here:
ja...@google.com <ja...@google.com> #14
Thank you for reporting this issue. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
[Deleted User] <[Deleted User]> #15
ja...@google.com <ja...@google.com> #16
ca...@gmail.com <ca...@gmail.com> #17
you need press charges against who ever fraudulently got access to my
account by your company
On Mon, Oct 12, 2020, 4:08 PM <buganizer-system@google.com> wrote:
ja...@google.com <ja...@google.com> #18
lb...@gmail.com <lb...@gmail.com> #19
@18 I tried to see which apps have it, hoping to see if there is a connection between it being true, and apps that I can't reach its app-info screen.
If you are indeed curious, I've written a question about it on StackOverflow:
Currently my suspicion is that it's not related at all, and that such apps are found via packageManager.getInstalledModules, yet only if "isHidden" is set to true.
I can't prove it though, because the docs don't say it at all. In fact the docs barely say anything about any of these fields and what they mean in the end, let alone to the app-info screen.
The only clue I got was from Google, of
"com.google.android.ext.services is mainline module, so Settings doesn't provide detail app info for it."
So that's how I conducted this idea and from where I started the research.
ja...@google.com <ja...@google.com> #20
Thank you for the update. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
ca...@gmail.com <ca...@gmail.com> #21
On Tue, Oct 13, 2020, 3:23 PM <buganizer-system@google.com> wrote:
io...@google.com <io...@google.com> #22
If an app is in fact APEX, this is the way to check if it's possible to reach its app-info screen or not?
APEX is a new file format that was introduce in Android 10. For more information on the file format and some background on the design decisions you can refer to
You can think of apex files as parts of the system that can be updated by an installer application outside of an OTA. Since apex file are actually apps, they don't have an app-info screen.
@12 I think on API 29 indeed it doesn't work, and on API 30 it does work. Odd.
As I can see in packageManager.getInstalledPackages(PackageManager.MATCH_APEX)
not to return any apex packages.
lb...@gmail.com <lb...@gmail.com> #23
Would filtering by modules alone, instead of APEX, be enough, to avoid seeing apps that don't have app-info screen, just like on the settings app?
As for checking on various APIs, I've tested on a device with API 29, and I think what you wrote it needs proper testing :
For some reason it showed that `getInstalledPackages(PackageManager.MATCH_APEX)` and `packageManager.getInstalledPackages(0)` returns the exact same number of apps.
Checking further, putting each of these lists into a HashSet of package-names, I've found that they indeed they are identical.
This was tested on a device with a custom ROM.
See attached.
So, currently, the API seems illogical for both API 29 and API 30:
- On API 29, it returns the exact same list as without this flag, and all are marked as non-APEX.
- On API 30, seems to work fine. It includes both normal apps and APEX apps
Can you please check on a normal device with Android 10?
ca...@gmail.com <ca...@gmail.com> #24
not have an Android 10 so can you please stop giving me permissions for
these people to hack onto my phone they already are on it I'm trying to get
them off please stop giving permissions
On Fri, Oct 30, 2020, 1:40 AM <buganizer-system@google.com> wrote:
ja...@google.com <ja...@google.com> #25
Hello
You may unsubscribe from email alerts of this issue using the link below
lb...@gmail.com <lb...@gmail.com> #26
Those seem to keep coming and nobody stops them.
io...@google.com <io...@google.com> #27
@22 Are those the only apps that I can find that also don't have app-info screen? Would filtering by modules alone, instead of APEX, be enough, to avoid seeing apps that don't have app-info screen, just like on the settings app?
ACTION_APPLICATION_DETAILS_SETTINGS
is not supported for apexes. From my local experiments it also seems that apks are not required to support this intent as well.
As for checking on various APIs, I've tested on a device with API 29, and I think what you wrote it needs proper testing : For some reason it showed that
getInstalledPackages(PackageManager.MATCH_APEX)
andpackageManager.getInstalledPackages(0)
returns the exact same number of apps.
Whether apex is supported is configured on per-device basis. You can query ro.apex.updatable
property to check if your testing device supports apex format.
Description
- Steps to reproduce the problem (including sample code if appropriate).
There is a field for PackageInfo of "isApex", but no matter how you try to get a list of installed apps that has it set to true, all is set to false.
Try it:
thread {
val apexApps = packageManager.getInstalledPackages(PackageManager.MATCH_APEX)
val allApps=packageManager.getInstalledPackages(0)
Log.d("AppLog", "apexApps:${apexApps.size} allApps:${allApps.size}")
apexApps.forEach {
if (it.isApex)
Log.d("AppLog", "${it.packageName} isApex?${it.isApex}")
}
}
- What happened.
If you look at apexApps , it just shows the same list of allApps, and all have isApex set to false.
- What you think the correct behavior should be.
We should be able to differentiate between them.