diff options
| author | Andrew Grieve <agrieve@google.com> | 2018-02-13 23:27:50 -0500 |
|---|---|---|
| committer | Richard Coles <torne@google.com> | 2018-03-06 17:28:47 +0000 |
| commit | 4700befb26f078ba77eedf07ddb3d85f095b2b33 (patch) | |
| tree | 60071b15a9f471b625074674c2c18a27a4ebd193 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | e84c506fc3b7cc962fac407f465e46e8a6b969e8 (diff) | |
Add Application.getProcessName()
This information is already available to non-sandboxed processes via
ActivityManager.getRunningAppProcesses(). However, performing an IPC and
iterating processes is quite cumbersome. See other alternatives devs have tried:
https://stackoverflow.com/questions/19631894/is-there-a-way-to-get-current-process-name-in-android
My specific motivation for exposing this information more directly is to
be able to perform process-specific initialization logic in
Application.attachBaseContext():
https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/ChromeApplication.java?rcl=ac2e180a1265f88dd4030bb35d69f5d0b2dc488d&l=54
Bug: 73344323
Test: Same code that's used in Chrome via reflection.
Change-Id: I83cec468458078e3fa183427a039869f74539c3d
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions