Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial


Crash report from Apple but can nor reproduce the error

My app has been rejected as it was crashing on launch. I have tried to reproduce the error but had no luck.

This is the crash report. Has anybody else experienced this?

Incident Identifier: 70B63C07-2EC9-4CA6-883C-7E6DC1FC28F1
CrashReporter Key:   e507fa34ffcb22f0c5c51a0e7631d57931794afb
Hardware Model:      xxx
Process:             ReactionTime [485]
Path:                /private/var/mobile/Containers/Bundle/Application/1F000700-CD22-4821-87AE-2EF8888953BC/ReactionTime.app/ReactionTime
Identifier:          co.uk.smudgeinc.reactiontimer
Version:             2 (4.0)
Code Type:           ARM-64 (Native)
Parent Process:      launchd [1]

Date/Time:           2014-10-02 14:03:10.138 -0700
Launch Time:         2014-10-02 14:03:10.130 -0700
OS Version:          iOS 8.0.2 (12A405)
Report Version:      105

Exception Codes: 0x0000000000000001, 0x00000001200dd088
Triggered by Thread:  0

Dyld Error Message:
  Library not loaded: @rpath/libswiftCore.dylib
  Referenced from: /private/var/mobile/Containers/Bundle/Application/1F000700-CD22-4821-87AE-2EF8888953BC/ReactionTime.app/ReactionTime
  Reason: no suitable image found.  Did find:
    /private/var/mobile/Containers/Bundle/Application/1F000700-CD22-4821-87AE-2EF8888953BC/ReactionTime.app/Frameworks/libswiftCore.dylib: mmap() error 1 at address=0x1000F0000, size=0x00194000 segment=__TEXT in Segment::map() mapping /private/var/mobile/Containers/Bundle/Application/1F000700-CD22-4821-87AE-2EF8888953BC/ReactionTime.app/Frameworks/libswiftCore.dylib
  Dyld Version: 353.5

Binary Images:
0x1200dc000 - 0x120103fff dyld arm64  <cde4667c8a4a3f80b7076a4766ee7205> /usr/lib/dyld
0x185ad8000 - 0x185e33fff CoreFoundation arm64  <ead15232d65b3139ba4866e7adbb5663> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
0x185e34000 - 0x185f96fff CoreGraphics arm64  <fe7274c9c42932baa9c2182f84f6ec57> /System/Library/Frameworks/CoreGraphics.framework/CoreGraphics
0x1869d4000 - 0x186c28fff Foundation arm64  <aad23ffe921534c9bb3fd8814a33b0e9> /System/Library/Frameworks/Foundation.framework/Foundation
0x18a134000 - 0x18a1bffff Social arm64  <e63d277e11f43be980638030f382403f> /System/Library/Frameworks/Social.framework/Social
0x18a2dc000 - 0x18a2f4fff StoreKit arm64  <58c17c55d2c5318c850df4534ca85544> /System/Library/Frameworks/StoreKit.framework/StoreKit
0x18a370000 - 0x18acd8fff UIKit arm64  <406f392b43b23f7daaa5c4345c8be709> /System/Library/Frameworks/UIKit.framework/UIKit
0x18afb8000 - 0x18aff1fff iAd arm64  <b03271d745ac3ef3824c39e0a8a7a1f0> /System/Library/Frameworks/iAd.framework/iAd
0x195b4c000 - 0x195b4dfff libSystem.B.dylib arm64  <debe5bcf0a6d31898e6b46412acfd1c0> /usr/lib/libSystem.B.dylib
0x196648000 - 0x196844fff libobjc.A.dylib arm64  <88bda32a9df13740ba61bef95d96a2b2> /usr/lib/libobjc.A.dylib


1 Answer

I encountered the same problem (I've been trying to publish an update for my app the whole day).

But take a look at this. It's not a fix, just more info.

That's a shame. Is it just a case of waiting until Apple fix it then?

Yeah, it certainly looks that way.

Oh that's a shame. Thanks for your help.

I assume Apple are aware of this issue are they?

They should be. A lot of developers have submitted reports. But it never hurts to report things like this again. I've submitted a report this morning.

Okay. I will submit one too. Thanks again

Hello, I was just wondering if you knew if this error has been fixed yet?


Yeah, it has. Apple fixed the issue on October 4th (next day). You can resubmit the binary.

Great! Thanks for your help