Samsung Galaxy S8 GennyMotion Simulator UnsatisfiedLinkError

We have a Samsung Galaxy S8 user that complains that the app will not open and closes repeatedly.  We tried loading the app on a Genymotion S8 simulator and saw the same thing happening.  Here’s what the logs show:

07-26 15:24:27.613  3084  3084 D AndroidRuntime: Shutting down VM 07-26 15:24:27.615  3084  3084 E AndroidRuntime: FATAL EXCEPTION: main 07-26 15:24:27.615  3084  3084 E AndroidRuntime: Process: com.Bridge, PID: 3084 07-26 15:24:27.615  3084  3084 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/app/tech.ixn.nathanc.Bridge-1/lib/arm/liblua.so" has unexpected e\_machine: 40 07-26 15:24:27.615  3084  3084 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:977) 07-26 15:24:27.615  3084  3084 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1530)

Any ideas on how to resolve this?

I went and bought a Samsung Galaxy S8 and it runs the app perfectly.  Must be a weird GenyMotion issue.  I did have to install an ARM translator to get the APK to install … perhaps this issue is just related to weird emulation issues between my mac and Genymotion.

Do you know much more about the user’s S8? 

Could it be jailbroken?

Could some vendor ware be interfering with things?

Rob

Nope – I don’t think they had an unlocked S8.  I bought an unlocked S8 and tested on that and everything is good.  I think this got diagnosed as an S8 issue prematurely and is probably an application bug.  :/

I went and bought a Samsung Galaxy S8 and it runs the app perfectly.  Must be a weird GenyMotion issue.  I did have to install an ARM translator to get the APK to install … perhaps this issue is just related to weird emulation issues between my mac and Genymotion.

Do you know much more about the user’s S8? 

Could it be jailbroken?

Could some vendor ware be interfering with things?

Rob

Nope – I don’t think they had an unlocked S8.  I bought an unlocked S8 and tested on that and everything is good.  I think this got diagnosed as an S8 issue prematurely and is probably an application bug.  :/