Crash with crosswalk build v4.4.0 on x86 devices


#1

Hello the Community,

We have an issue with a recent version of our app (published last week) build v4.4.0 Google Play (Crosswalk, ARM and x86)

This is the crash logs from the Google Play Console :

java.lang.RuntimeException: Unable to create application com.appgyver.runtime.standalone.chromium.StandaloneChromiumApplication: java.lang.RuntimeException: Please have your activity extend XWalkActivity for shared mode
	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4770)
	at android.app.ActivityThread.-wrap1(ActivityThread.java)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1421)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:148)
	at android.app.ActivityThread.main(ActivityThread.java:5480)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
Caused by: java.lang.RuntimeException: Please have your activity extend XWalkActivity for shared mode
	at org.xwalk.core.XWalkCoreWrapper.initEmbeddedMode(XWalkCoreWrapper.java:214)
	at org.xwalk.core.XWalkPreferences.reflectionInit(XWalkPreferences.java:280)
	at org.xwalk.core.XWalkPreferences.setValue(XWalkPreferences.java:119)
	at com.appgyver.webview.XWalkRuntimeConfig.<init>(XWalkRuntimeConfig.java:22)
	at com.appgyver.runtime.standalone.chromium.StandaloneChromiumApplication.onCreate(StandaloneChromiumApplication.java:12)
	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1013)
	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4767)
	...

It’s only (for the moment…) with Zenfone 2 devices (x86 achitecture), and we had no problem with the previous version of the app (build v4.2.1 Google Play (Crosswalk, ARM and x86))
There were no significant changes to generate such an error between this version and the previous one.

Have you any information about it and
Anyone knows if the problem exists with build v4.3.2 (Crosswalk, ARM and x86) ?

Thank you for your help,

David