Replies: 1 comment
-
Here is more discussion: https://users.rust-lang.org/t/android-data-app-directory/133381/11 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Let's say some app
com.qux.bar
has some assets (app's installation files) like{project}/scenes/waterfall.webp
(not statically incorporated throughinclude_bytes!
in Rust).According to AI information, these files reside in
/data/app/{...}
, and not/data/data/{ID}
. I've downloaded ZArchiver in my Android phone (not rooted) to see what's in/data/app/{...}
, but it turns out it's structured likedata/
app/
~~-ZDrxMxFFkgo...bg==/
com.instagram.android-QD9SphAoXwr...Hg==/
lib/
oat/
base.apk
I'm not sure if this is what is considered an "installation directory" (in Windows it's generally the place where executable resides plus files that aren't fixed in the RAM like heavy icon assets, object descriptions and scenes).
I know that Adobe AIR has the concept of
app://
URLs, which are relative to the app's "installation directory". I wanted to produce the same in Rust, but am a bit confused about the Android case.We have at least
android_activity::AndroidApp::internal_data_path()
, but it probably yields something like/data/data/{ID}
, and as I've shown,data/app/...
entries seem to have a base64 encoding inside them.Beta Was this translation helpful? Give feedback.
All reactions