Skip to main content
March 31, 2013
Question

java.lang.UnsatisfiedLinkError: nativeSurfaceCreated

  • March 31, 2013
  • 5 replies
  • 4559 views

Some users can't start app and getting the following error with Air 3.6:

java.lang.UnsatisfiedLinkError: nativeSurfaceCreated

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

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

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

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

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

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

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

at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2583)

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

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

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

at java.lang.reflect.Method.invokeNative(Native Method)

at java.lang.reflect.Method.invoke(Method.java:511)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:809)

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

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

As I could find in Google, this happenes when device is low on space and enbeded air runtime can be loaded.

Any help or ideas how can this be fixed?

Thank you.

This topic has been closed for replies.

5 replies

Participant
December 13, 2020

Ps touch opan nahi ho rahi

Participant
November 26, 2015

We are getting the same issue through app crash reports. The app crashes only on android 6.0 while it works just fine on lower android versions. We got this report through few users using Nexus 5 with Android Marshmellow (6.0). This happened after we updated our apps targetSDKVersion to 23 in app-xml. The app starts working fine on Nexus 5 if we set its targetSDKVersion back to 19. Is there any solution found to this problem? Hope the information I shared helps the Adobe tech team to find a quick solution. Please do update if you found any solution.

deesharm
Adobe Employee
Adobe Employee
November 26, 2015

Hi,

Please try packaging your application with latest Adobe AIR Beta Build. ( Adobe AIR 20 Beta | application development - Adobe Labs )

Hope, it will resolve your problem.

Thanks,

Adobe AIR Team

Participant
November 26, 2015

Thanks for the solution. Are you sure that using AIR Beta Build will solve the issue? We cannot implement a trial-and-error solution as we dont have any device to test this solution and we cant update our app again and again and ask our users if the problem is solved on their device. I also posted a reply on a similar question on the forum here, where a developer commented that using AIR 20 did not solve this issue for them.

Participant
August 17, 2015

So what is th solution for this ? and i have lots of space on the device. and the error is coming on almost everyphone i tested my apps on. plz help..

Participant
April 6, 2013

I am also interested in this. I have 2 applications on Google market packaged as captive runtime. Both of them reporting this error on some of the devices.

I have 2 guesses what it might be:

1. Device does't have Adobe Air support

2. Insufficient memory to run Adobe Air

Adobe Employee
April 1, 2013

Could you please share the device and Android version on whcih you are getting this.

April 1, 2013

This problem was reported by users through Android report feature, unfortunately they didn't provide neither device nor Android version.

Don't know what to do with such report.

Participant
April 9, 2013

Hi,

Did you package your app with captive runtime because captive runtime seems to "unzip" some file when the application start and if the user phone haven't enough memory space the AIR runtime is not fully installed so that why unsatisfied link errors occurded.