You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the option:
< haxeflag name="-dce" value="full" / >
The app renders correctly, but as soon as I touch the screen, the app crashes. I compiled with the verbose option, and found this:
W/Binder ( 1960): Caught a RuntimeException from the binder stub implementation.
W/Binder ( 1960): java.lang.NullPointerException
W/Binder ( 1960): at android.inputmethodservice.IInputMethodWrapper.setSessionEnabled(IInputMethodWrapper.java:280)
W/Binder ( 1960): at com.android.internal.view.IInputMethod$Stub.onTransact(IInputMethod.java:129)
W/Binder ( 1960): at android.os.Binder.execTransact(Binder.java:404)
W/Binder ( 1960): at dalvik.system.NativeStart.run(Native Method)
My test app went from 10,42mb to 8,75mb, so I think the support of dce is very important. On mobile every bit counts.
The text was updated successfully, but these errors were encountered:
RafaelOliveira
changed the title
OpenFL / Android crashs on first touch with dce -full
OpenFL / Android crashes on first touch with dce -full
Sep 16, 2014
With the option:
< haxeflag name="-dce" value="full" / >
The app renders correctly, but as soon as I touch the screen, the app crashes. I compiled with the verbose option, and found this:
W/Binder ( 1960): Caught a RuntimeException from the binder stub implementation.
W/Binder ( 1960): java.lang.NullPointerException
W/Binder ( 1960): at android.inputmethodservice.IInputMethodWrapper.setSessionEnabled(IInputMethodWrapper.java:280)
W/Binder ( 1960): at com.android.internal.view.IInputMethod$Stub.onTransact(IInputMethod.java:129)
W/Binder ( 1960): at android.os.Binder.execTransact(Binder.java:404)
W/Binder ( 1960): at dalvik.system.NativeStart.run(Native Method)
My test app went from 10,42mb to 8,75mb, so I think the support of dce is very important. On mobile every bit counts.
The text was updated successfully, but these errors were encountered: