Skip to main content
Participant
December 20, 2013
Question

App with air embedded causing problems on a Galaxy Nexus 5 - UnsatisfiedLinkError

  • December 20, 2013
  • 1 reply
  • 1176 views

Hi there,

I've recently launched a game on the Google Play store which has been working fine until recently, I received an error report from a Galaxy Nexus 5 user running Android 4.4. The report is below. I've read elsewhere that the issue could be caused by a lack of space on the device but this seems unlikely (the owner sits opposite me in the studio and has only just bought the phone).

I'd appreciate any help on how best to tackle this issue, perhaps advice on whether it is better to not embed the AIR runtime and have customers download it separately? Ideally I'd prefer not to go down this route but will do whatever is necessary to ensure players can run the app!

It's very frustrating as the app has been running great on various Android devices until now. (the iPhone version is also out and no issues as of yet - probably because it's compiled differently for iOS).

The app was created and exported from Flash CS6 using AIR 3.4. I've udated the app now using AIR 3.9.0.1200 which throws up a warning about using captive runtime - another hint that I can't embed AIR anymore??

Error report follow:

java.lang.UnsatisfiedLinkError: Native method not found: com.adobe.air.AIRWindowSurfaceView.nativeSurfaceCreated:()V

at com.adobe.air.AIRWindowSurfaceView.nativeSurfaceCreated(Native Method)

at com.adobe.air.AIRWindowSurfaceView.surfaceCreated(AIRWindowSurfaceView.java:718)

at android.view.SurfaceView.updateWindow(SurfaceView.java:572)

at android.view.SurfaceView.access$000(SurfaceView.java:86)

at android.view.SurfaceView$3.onPreDraw(SurfaceView.java:175)

at android.view.ViewTreeObserver.dispatchOnPreDraw(ViewTreeObserver.java:847)

at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1871)

at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1000)

at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5670)

at android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)

at android.view.Choreographer.doCallbacks(Choreographer.java:574)

at android.view.Choreographer.doFrame(Choreographer.java:544)

at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)

at android.os.Handler.handleCallback(Handler.java:733)

at android.os.Handler.dispatchMessage(Handler.java:95)

at android.os.Looper.loop(Looper.java:136)

at android.app.ActivityThread.main(ActivityThread.java:5017)

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:779)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)

at dalvik.system.NativeStart.main(Native Method)

Thanks in advance,

Johnny - Media Wow

This topic has been closed for replies.

1 reply

MediawowAuthor
Participant
December 20, 2013

Thanks for the heads up, I'll give that a go (fingers crossed)

MediawowAuthor
Participant
December 23, 2013

A newer version of AIR seems to have fixed the issue (phew eh!). I was actually still using AIR 3.4 when publishing so I changed to 3.9 (until the full release of AIR 4). Thanks for the help flexercised!