You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
The text was updated successfully, but these errors were encountered:
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.
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 ason-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 withaccess denied
.Why it doesn't have such permissions ?
The text was updated successfully, but these errors were encountered: