UIResponder instead null

This commit is contained in:
Vladimir Enchev
2015-08-04 11:48:23 +03:00
parent 40f39e61da
commit 5e2f184568

View File

@@ -205,7 +205,7 @@ exports.start = function () {
// This try-catch block here will catch JavaScript errors but no Objective C ones. // This try-catch block here will catch JavaScript errors but no Objective C ones.
// TODO: We need to implement better error handling for our native calls and to use the "error" parameter of the iOS APIs. // TODO: We need to implement better error handling for our native calls and to use the "error" parameter of the iOS APIs.
UIApplicationMain(0, null, null, exports.ios && exports.ios.delegate ? NSStringFromClass(exports.ios.delegate) : null); UIApplicationMain(0, null, null, exports.ios && exports.ios.delegate ? NSStringFromClass(exports.ios.delegate) : NSStringFromClass(UIResponder));
} }
catch (error) { catch (error) {
// At this point the main application loop is exited and no UI May be created. // At this point the main application loop is exited and no UI May be created.