android:extractNativeLibs="true" for Dynamic Feature Module

bundle-tool version 0.9.0

Currently I have some precompiled libs in main/jniLibs/arch/*.so and specifying

android:extractNativeLibs=“true”

in AndroidManifest.xml to extract them on install, now i want to move those libs to Dynamic Feature Module. where i specified bundle manifest as below

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:dist="http://schemas.android.com/apk/distribution"
    package="in.canews.nativelibs">

    <dist:module
        dist:instant="false"
        dist:title="@string/title_nativelibs">
        <dist:delivery>
            <dist:on-demand />
        </dist:delivery>
        <dist:fusing dist:include="true" />
    </dist:module>
    <application android:extractNativeLibs="true"/>
</manifest>

but on install of that feature libs are not extracted to libs folder of app.

[plecesne]

That seems to be working as intended.

If the native libraries belong to the dynamic feature and the dynamic feature is uninstalled, it is expected for the native libraries to be removed as well. The uninstallation is always deferred so it’s possible that the extracted native libraries remain a bit longer in the local storage, but they effectively should not be used.

[eakteam]

Is splitcompat dir has exec permissions targetting Api 29(Android 10) ? @canewsin

I believe it has such permission for application user. @ymakhno

It doesn’t have exec permissions, so the only way to execute executable native libs is to make Dynamic Feature module install-time. In that way it will extract native libs to default app native libs directory and you can execute from there.

Also strongly recommend to make /data/data/<package-name>/files/splitcompat able to execute native libs.