Crash due to localeconv?

[Aleix Pol]

No, it shouldn't matter as long as when compiling you link against the
right set of libraries.

I don't know what library it is, if it's looking for localeconv, I
guess localeconv.so or liblocaleconv.so?

Aleix

On Thu, Nov 10, 2016 at 4:22 PM, Jasem Mutlaq <mutlaqja at ikarustech.com> wrote:
> How do we include the library in the APK exactly? And what library is
> exactly? We're using androiddeployqt
>
> I saw the gimp issue, and we can increase the API Level (which is set at 15
> now). but then we'd lose about 30% of the market (see
> https://developer.android.com/about/dashboards/index.html) so it would be
> better to resolve this and no there are no choices then we'd bump the API
> level. I'm using the latest NDK from Google but should that matter if the
> Target API Level is set to 15?
>
> On Thu, Nov 10, 2016 at 6:15 PM, Aleix Pol <aleixpol at kde.org> wrote:
>>
>> Hi,
>> I haven't seen this error before, maybe the apk should include the
>> library?
>>
>> A fast search suggests that this is on API >=21.
>> https://github.com/Rupan/gmp/issues/6
>>
>> Maybe your application or Qt are compiled with a too new NDK version?
>>
>> Aleix
>>
>> On Thu, Nov 10, 2016 at 9:46 AM, Jasem Mutlaq <mutlaqja at ikarustech.com>
>> wrote:
>> > Ok, could this be due perhaps to target API Level settings? Currently,
>> > we
>> > set it to 15. Should that be increased?
>> >
>> > On Thu, Nov 10, 2016 at 11:32 AM, Jasem Mutlaq <mutlaqja at ikarustech.com>
>> > wrote:
>> >>
>> >> Hello,
>> >>
>> >> After submitting KStars Lite to the Google Play Store last week, I've
>> >> been
>> >> getting this crash report:
>> >>
>> >> java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol
>> >> "localeconv" referenced by "libkstars.so"...
>> >> at java.lang.Runtime.loadLibrary(Runtime.java:364)
>> >> at java.lang.System.loadLibrary(System.java:526)
>> >> at
>> >>
>> >> org.qtproject.qt5.android.bindings.QtLoader.loadApplication(QtLoader.java:244)
>> >> at
>> >> org.qtproject.qt5.android.bindings.QtLoader.startApp(QtLoader.java:647)
>> >> at
>> >>
>> >> org.qtproject.qt5.android.bindings.QtActivityLoader.onCreate(QtActivityLoader.java:181)
>> >> at
>> >>
>> >> org.qtproject.qt5.android.bindings.QtActivity.onCreate(QtActivity.java:269)
>> >> at android.app.Activity.performCreate(Activity.java:5459)
>> >> at
>> >>
>> >> android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1093)
>> >> at
>> >>
>> >> android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2364)
>> >> at
>> >>
>> >> android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2458)
>> >> at android.app.ActivityThread.access$900(ActivityThread.java:172)
>> >> at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1305)
>> >> at android.os.Handler.dispatchMessage(Handler.java:102)
>> >> at android.os.Looper.loop(Looper.java:146)
>> >> at android.app.ActivityThread.main(ActivityThread.java:5598)
>> >> at java.lang.reflect.Method.invokeNative(Native Method)
>> >> at java.lang.reflect.Method.invoke(Method.java:515)
>> >> at
>> >>
>> >> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1283)
>> >> at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1099)
>> >> at dalvik.system.NativeStart.main(Native Method)
>> >>
>> >> Anyone know how to resolve this for Qt/KDE apps?
>> >>
>> >> --
>> >> Best Regards,
>> >> Jasem Mutlaq
>> >>
>> >
>> >
>> >
>> > --
>> > Best Regards,
>> > Jasem Mutlaq
>> >
>
>
>
>
> --
> Best Regards,
> Jasem Mutlaq
>