From 3d42e87ea1a1d4a93f0f10d79117dab328c57f3e Mon Sep 17 00:00:00 2001
From: Vladimir Enchev <vladimir.enchev@telerik.com>
Date: Tue, 4 Aug 2015 15:16:34 +0300
Subject: [PATCH] use inherited class instead of UIResponder

---
 application/application.ios.ts | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/application/application.ios.ts b/application/application.ios.ts
index 1743505a7..aae7b25a7 100644
--- a/application/application.ios.ts
+++ b/application/application.ios.ts
@@ -9,6 +9,10 @@ global.moduleMerge(appModule, exports);
 
 export var mainModule: string;
 
+class Responder extends UIResponder {
+    //
+}
+
 class Window extends UIWindow {
 
     private _content: view.View;
@@ -206,7 +210,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) : NSStringFromClass(UIResponder));
+        UIApplicationMain(0, null, null, exports.ios && exports.ios.delegate ? NSStringFromClass(exports.ios.delegate) : NSStringFromClass(Responder));
     }
     catch (error) {
         // At this point the main application loop is exited and no UI May be created.