Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SplitCompat doesn't have executable permissions for extracted native libs #267

Closed
eakteam opened this issue Feb 7, 2022 · 1 comment
Closed

Comments

@eakteam
Copy link

eakteam commented Feb 7, 2022

Regarding to that bug report : #155 , SplitCompat native libs directory should allow executing native libs from the directory where they are extracted.

In normal circumstances if the Dynamic Feature Module is configured as install-time we are able to execute native libs using :
context.getApplicationInfo().nativeLibraryDir, "libexampleexec.so", but if it is configured as on-demand and trying to execute native libs from that directory : context.filesDir.path + File.separator + "splitcompat" + File.separator + MainApplication.versionCode + File.separator + "native-libraries" it fails with access denied.

Why it doesn't have such permissions ?

@ymakhno
Copy link
Collaborator

ymakhno commented Apr 1, 2022

This issue doesn't relate to bundletool.

I believe you can not execute any binary inside /data/data/... folder since Android Q as this is Android security constraint. In #155 question was: Is splitcompat dir has exec permissions?, directory itself has such permission, files inside can not have it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants