Skip to main content
stolennickname
stolennickname
Inspiring
Dec 18, 2014 12:30 AM UTC
Answered

iOS Simulator won't launch, id: entry point (start) undefined error

I am still unable to launch the iOS Simulator after updating to AIR 16.0.0.245. I am seeing the following error on performing a debug run:

Create iOS Package

id: entry point (start) undefined. Usually in crt1.o for architecture i386

Compilation failed while executing: id64

My adt parameters seem OK, and pathing to SDK (iOS 8.1) is good. Debugging on device works fine. This is occurring in a pure ActionScript project that makes heavy use of Stage3D/Starling/Feathers.

Can someone point to some troubleshooting on this particular issue?

This topic is closed to new replies. Start a new post to keep the conversation going.
abmishra
abmishraCorrect answer
Adobe Employee
Dec 22, 2014 6:39 PM UTC

This issue is fixed in latest beta (16.0.0.250), please try with the same and let us know if you face any issue.

View reply

4 replies

Alexey Kornilov
Inspiring
Dec 19, 2014 7:16 AM UTC

I had the same issue with 16.0.0.245. After I added platform.xml for my ANES everything started working. Settings are:

<?xml version="1.0"?>

<platform xmlns="http://ns.adobe.com/air/extension/16.0">

    <sdkVersion>8.1</sdkVersion>

    <linkerOptions>

        <option>-ios_version_min 7.0</option>

        <option>-ObjC</option>

    </linkerOptions>

</platform>

Please try this in you environment to confirm. Of course if you are compiling ANEs for yourself.

Thanks

Translate
abmishra
Adobe Employee
abmishraCorrect answer
Adobe Employee
Dec 22, 2014 6:39 PM UTC

This issue is fixed in latest beta (16.0.0.250), please try with the same and let us know if you face any issue.

Translate
erwg34yv3
Participant
Apr 27, 2015 6:39 AM UTC

I still get this error. tested with Air 16.0.0.292 & 17.0.0.144 (same on both)

app runs fine on device, using SDK 8.3

have no Additional ADT options

Translate
abmishra
Adobe Employee
abmishra
Adobe Employee
Dec 18, 2014 3:39 AM UTC

Thanks for reporting this, this is known to us and next release will have a fix for this.

Translate
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices