Skip to main content
Inspiring
January 10, 2012
Question

Native Extensions crash in Release build

  • January 10, 2012
  • 4 replies
  • 3015 views

When I test in debugger quick the Native Extensions work fine. When I debug or release in a standard build then the app crashes... Has anyone experienced this?

The native extensions that seems to be crashing only on release mode is

FlurryAnalytics https://github.com/StickSports/ANE-Flurry-Analytics

No errors are thrown, app just terminates.

This is on iOS/ IPhone 4

This topic has been closed for replies.

4 replies

Participant
August 20, 2012

Have the same issue, but running on Android device, and this is the log:

08-19 17:37:58.311: W/System.err(14317): java.lang.NullPointerException

08-19 17:37:58.311: W/System.err(14317):     at java.io.File.fixSlashes(File.java:185)

08-19 17:37:58.311: W/System.err(14317):     at java.io.File.<init>(File.java:134)

08-19 17:37:58.311: W/System.err(14317):     at com.adobe.air.JavaTrustStoreHelper.getX509TrustManagerFactory(JavaTrustStoreHelper.java:81)

08-19 17:37:58.321: W/System.err(14317):     at com.adobe.air.JavaTrustStoreHelper.getX509TrustManager(JavaTrustStoreHelper.java:110)

08-19 17:37:58.321: W/System.err(14317):     at com.adobe.air.JavaTrustStoreHelper.enumerateRootCAs(JavaTrustStoreHelper.java:195)

08-19 17:37:58.331: W/System.err(14317):     at dalvik.system.NativeStart.run(Native Method)

Participant
January 12, 2012

Have the same issue, -target ipa-test-interpreter works fine, ipa-test crashes the app, ipa-ad-hoc freezes the app (using NativeAlert https://github.com/mccormicka/NativeAlert).

this issue seems similar: http://forums.adobe.com/thread/946702 ...

K2xL_comAuthor
Inspiring
January 14, 2012

hmm.. anyone from adobe reading this? i'm on windows

Participant
January 14, 2012

got it !

check the correct answer on this thread: http://forums.adobe.com/message/4008439#4008439

basicly, the swc should have link type 'external'

( …when using FDT, on the swc : 'source > remove from export' is not sufficient to exclude it, in the launch profile 'Auto exclude (-externs)' must be checked also! )