Xcode crashes when running on any iOS 8 Simulator

Question

Created Nov ’15

Replies 6

Boosts 0

Views 1.1k

Participants 3

Whenever I try to run my app on any iOS 8.X based simulator (regardless of hardward selected) it hard crashes and gives me the following report:

Process: Xcode [24379]

Path: /Applications/Xcode.app/Contents/MacOS/Xcode

Identifier: com.apple.dt.Xcode

Version: 7.1.1 (9081)

Build Info: IDEFrameworks-9081000000000000~5

App Item ID: 497799835

App External ID: 814167395

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Xcode [24379]

User ID: 502

Date/Time: 2015-11-19 21:15:09.651 -0700

OS Version: Mac OS X 10.10.5 (14F27)

Report Version: 11

Anonymous UUID: D2C86FCA-00EC-1981-5327-66B02B309CC5

Sleep/Wake UUID: 5AA20BFE-6BBC-4978-BD70-16D58F20081D

Time Awake Since Boot: 100000 seconds

Time Since Wake: 27000 seconds

Crashed Thread: 19

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:

ProductBuildVersion: 7B1005

ASSERTION FAILURE in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-9073/DVTFoundation/Multicore/DVTFuture.mm:411

Details: Attempted to transition to the succeeded state twice.

Progress: Initial

Result: 1

Error: (null)

Started at: 0 0x00000001094ca81e -[DVTFuture init] (in DVTFoundation)

As I am very new to developing on Apple platforms, I don't have a clue where to start to diagnose this issue. I can tell you that the target platform in my build settings is iOS 7, that I am using the Facebook SDK framework, CocoaPods, and the Parse SDK. At one point in the early stages of my app development it would run fine on just about any platform but without knowing the underlying cause I'm not sure where to start looking.

I can post the remainder of the report upon request, it's just very lengthly and I felt it might be better to start there.

Thanks for any help!

Boost

Answer 1

FridayDev OP

Nov ’15

Anybody?

0

Answer 2

Floating Wrench OP

Nov ’15

This appears to be a bug in the DVTFramework when running on the Simulator.

Many framsworks have different behavior or can crash when run in the simulator.

Have you tried contacting the developers of that framework?

0

Answer 3

FridayDev OP

Nov ’15

I think DVTFramework is a built-in framework. When I search my project for "DVT" I return no results. As well, googling "DVTFramework" returns quite a few others that had a crash at the same point but their error details were more solvable. Nothing with "Attempted to transition to the succeeded state twice."

0

Answer 4

Floating Wrench OP

Nov ’15

I am pretty sure it is not. It likely is included in one of the multiple third party frameworks you are using if you are not adding it yourself to your project framework dependencies. I do not know what version you are linking to, but it also appears to be quite old. Maybe someone with direct experience with this framework can comment.

"JULY 10 2003 -- DVT Corporation (Duluth, GA) has released FrameWork 2.6, which has numerous enhancements to the company's FrameWork software, the operating system for a wide range of machine-vision products. "Our FrameWork software brings both power and ease of use to the forefront for our customers," commented Bob Steinke, CEO of DVT."

If possible, I would encourage you to not use third party frameworks or development tools and stick to plain Xcode while you are learning. You have a lot of dependencies that may make it diificult to troubleshoot the origin of problems you encounter when you are just getting started. Also, targeting a more recent version than iOS 7 might be helpful.

You may also want to limit your development to running on the device for now. The simulator is useful to speed the development of user interfaces or general app flow, but it is not an emulator. You may be sidetracked by issues such as this which are solely a side effect of running in the simulator.

Good luck!

0

Answer 5

FridayDev OP

Nov ’15

Alright then, I suppose I'll just continue to test in iOS9 and hope this error resolves itself. Thanks!

0

Answer 6

Developer Tools Engineer OP

Apple

Nov ’15

File a radar with the full crash log.

0