Native lib in c for Android app on Galaxy A13 returns different value depending on build type (debug or release)

Viewed 16

I've an app that uses a native library to run some pretty simple calculations, mainly converting jbyteArray into char *, doing some vector calculations, and returning the result back into jbyteArray

The lib is written in c, and on most smartphones tested, the same input parameters yield the same results, whether it's a debug or release build.

But on a particular smartphone, namely a Samsung's Galaxy A13 on Android 12, with the same input parameters, the lib returns a different value.

This is totally unexpected.

Has anyone experienced a similar issue ? Why would a lib on a release build yields a value different than using a debug build ?

0 Answers
Related