From 5e2f18456865736b9fd3b6e0a6ef343a00b40d8b Mon Sep 17 00:00:00 2001
From: Vladimir Enchev <vladimir.enchev@telerik.com>
Date: Tue, 4 Aug 2015 11:48:23 +0300
Subject: [PATCH] UIResponder instead null

---
 application/application.ios.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/application/application.ios.ts b/application/application.ios.ts
index 368c6561d..79caabb77 100644
--- a/application/application.ios.ts
+++ b/application/application.ios.ts
@@ -205,7 +205,7 @@ exports.start = function () {
         // 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.
 
-        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) {
         // At this point the main application loop is exited and no UI May be created.