Exception Type: EXC_CRASH (SIGABRT)
This indicates that your app crashed because some code called abort. The is usually, but not always, caused by an unhandled language exception. And the presence of the Last Exception Backtrace section confirm that.
Last Exception Backtrace:
0 CoreFoundation … __exceptionPreprocess + 216 …
1 libobjc.A.dylib … objc_exception_throw + 56 …
2 Foundation … -[__NSConcreteURLComponents initWithURL:resolvingAgainstBaseURL:] + 304 …
3 Foundation … +[NSURLComponents componentsWithURL:resolvingAgainstBaseURL:] + 44 …
4 OrgCorescore …
5 OrgCorescore …
6 OrgCorescore …
7 OrgCorescore …
8 OrgCorescore …
9 OrgCorescore …
10 OrgCorescore …
11 UIKitCore … -[UIViewController _sendViewDidLoadWithAppearanceProxyObjectTaggingEnabled] + 104 …
Frame 11 suggests that the system is calling a view-did-load method on one of your view controllers. Frame 10 through 4 are your code. Frame 3 indicates that your code called an NSURLComponents, which then threw this exception. it’s likely that’s because the URL parameter you passed to the +componentsWithURL:resolvingAgainstBaseURL: was nil.
As to how things got that ways, it’s hard to say. To make progress here you need to symbolicate your code’s stack frames. See Adding Identifiable Symbol Names to a Crash Report.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
