Library that does not support 16 KB: base/lib/x86_64/libandroidlame.so

[JetmirAhmati]

i have expo app and installed there react-native-compressor. Now i got warning from google console that "Library that does not support 16 KB: base/lib/x86_64/libandroidlame.so" and as i researched a bit i got this feedback from chat gpt. Ahh, that’s the culprit 👉 libandroidlame.so (a native MP3 encoder library). It hasn’t been rebuilt with the -Wl,-z,max-page-size=16384 linker flag, so Google Play flags it.

⚠️ Why this happens

Expo/EAS already handles the 16 KB alignment for Hermes and official Expo libs.

But if you depend on third-party native modules (like react-native-compressor → it bundles android-lame), those may still ship .so files compiled with the old 4 KB alignment.

[github-actions[bot]]

👋 @JetmirAhmati Thanks for opening your issue here! If you find this package useful hit the star🌟!

[Jul1enF]

I have the exact same problem.

In my android expo build, libandroidlame.so does not respect 16kb pages and only react native compressor uses lame in my app.

Would very much like an update for this ! :)

[JetmirAhmati]

i am closing since this issue is currently on active in this PR #355

[Traviskn]

The pull request was closed, and this is still an issue. the November 2025 deadline is approaching soon, we will need a fix for the libandroidlame.so dependency.

[MubashirAlirecomune]

any progress on it?

[tunhnt2]

I have the same problem, is there any update?

[sleeper-luke]

I was able to fix this issue by adding this to my app/build.gradle. Basically replacing the non-compliant android lame dependency for this fork: https://github.com/kaushik-naik/TAndroidLame/pull/1

configurations.all {
    resolutionStrategy.dependencySubstitution {
        substitute(module('com.github.banketree:AndroidLame-kotlin'))
                .using(module('com.github.kaushik-naik:TAndroidLame:a485052f28'))
    }
}

from this comment: https://github.com/naman14/TAndroidLame/issues/31#issuecomment-3301982268

[DvzZDev]

Use the patch below whit patch-package, this fix the issue until the pr is merge. https://github.com/numandev1/react-native-compressor/pull/355#issuecomment-3180870738

[gkasireddy202]

I updated the version from 1.12.0 to 1.13.0, and the emulator returns a 16KB warning pop-up.

[numandev1]

Can someone create a PR using this patch: com.github.kaushik-naik:TAndroidLame:277c2ab4b0 ?

https://github.com/numandev1/react-native-compressor/pull/355

[carlosmellado]

Having the same issue :(

[iita71737]

I have the same problem, is there any update?

[Traviskn]

I was able to fix this issue by adding this to my app/build.gradle. Basically replacing the non-compliant android lame dependency for this fork: kaushik-naik/TAndroidLame#1

configurations.all {
    resolutionStrategy.dependencySubstitution {
        substitute(module('com.github.banketree:AndroidLame-kotlin'))
                .using(module('com.github.kaushik-naik:TAndroidLame:a485052f28'))
    }
}

from this comment: naman14/TAndroidLame#31 (comment)

this worked for me

[AndrianarivoAlpha]

Same issue!

[mGallee]

We are experiencing the same issue in our app :(

[francoangulo]

Any update on this? Google Play Store requires apps to compile with 16kb page support for Nov 1st , 2025

[carlosmellado]

Any update on this? Google Play Store requires apps to compile with 16kb page support for Nov 1st , 2025

I was able to fix it using the solution about replacing dependencies posted above. At least it works meanwhile we found another solution.

[gkasireddy202]

I have been waiting for this fix since last month, and it is still unresolved. I need to have this fixed in my app before November 1, 2025.

[carlosmellado]

I have been waiting for this fix since last month, and it is still unresolved. I need to have this fixed in my app before November 1, 2025.

@gkasireddy202 you have a solution above mate. I know it's not the ideal solution but it works while we find another fix for that. Use the dependency replacement on the gradle file. It will solve your issue and you'll be able to skip the play store warning.

Anyways, seems like if no one propose a solution this won't be solved because we're lots of us having this issue and we have no response 😅

[gkasireddy202]

@carlosmellado - Thanks for your reply. Can we expect the new release with this fix to be available within the next 10 days?

[carlosmellado]

@carlosmellado - Thanks for your reply. Can we expect the new release with this fix to be available within the next 10 days?

I'm not the developer mate, but as far as I see I won't expect that. What I did in my personal project is to apply this fix above and if the library is updated then I'll roll it back and update the library. But yeah, only my opinion 😅

[guruatdigni]

Please fix the issue.

[suschuk24]

There's an open PR for this issue, but the checks are failing because of a call to a deprecated action. Can someone bypass those checks and merge the PR?

Not all of us build locally, and so manually injecting code into the build.gradle file isn't a workable solution.