android how to download hearthstone directly to sd card

* An AsyncCallback can be given to the executeEndpointAsync method. In the native cpp library we use some external libraries (curl, jsoncpp, plog-logging, sqlite and tinyxml2).Īs requested, here the code of Wrapper.java: package ch. The ch.callCoreEndpointJNI is the entry point to our native cpp library. The line it points to however just reads as follows: import The Wrapper.java is the class which calls our native library. Through the google-play-console I got the following crash report: :Īt ch.callCoreEndpointJNI (Wrapper.java)Īt ch.a (Wrapper.java:9)Īt ch.a (Exam.java:46)Īt ch. (SubjectActivity.java:9)Īt ch. (SubjectActivity.java:213)Īt (Activity.java:7136)Īt (Activity.java:7127)Īt (Instrumentation.java:1272)Īt (ActivityThread.java:2908)Īt (ActivityThread.java:3063)Īt .execute (LaunchActivityItem.java:78)Īt .executeCallbacks (TransactionExecutor.java:108)Īt .execute (TransactionExecutor.java:68)Īt $H.handleMessage (ActivityThread.java:1823)Īt android.os.Handler.dispatchMessage (Handler.java:107)Īt android.os.Looper.loop (Looper.java:198)Īt (ActivityThread.java:6729)Īt .invoke (Method.java)Īt .RuntimeInit$n (RuntimeInit.java:493)Īt .ZygoteInit.main (ZygoteInit.java:876) However, the error still occurs in the same frequency like before. So I removed the 64bit libraries (the app still runs on all devices, because 64-bit architectures can also execute 32-bit libraries). I continued my online research and found this article, which suggests that the problem lies in the 64-bit libraries.

Unfortunately, this did not reduce the amount of crashes due to. Therefore they created a ReLinker library which will try to fetch the libraries from the compressed app: I have found this resource which points out that Android sometimes fails to unpack external libraries. I am a bit lost here, because I've tried already several things but so far I was not able to either reduce the number of occurrences nor to reproduce it on any of my devices.

I upload the app to the app store as an android-app-bundle and suspect that this could be the source of the problem. I've tested the app on my phone and on several emulators, including all the architectures. The app works fine on my device and on most user devices, however there is a crashing rate over 3 percent, mostly because of and occurring on Android versions 7.0, 8.1 as well as 9. Together with a friend I have created an Android app to organize school grades.

Android how to download hearthstone directly to sd card