From 1eda14b2efb233ce2bdfa7a31c663d6d7be25c3e Mon Sep 17 00:00:00 2001
From: "Pfeil, Scott Robert" <scott.pfeil3@verizonwireless.com>
Date: Fri, 13 Mar 2020 10:04:47 -0400
Subject: [PATCH] swift

---
 .../MainProtocols/MVMCoreViewManagerViewControllerProtocol.h  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/MVMCore/MVMCore/MainProtocols/MVMCoreViewManagerViewControllerProtocol.h b/MVMCore/MVMCore/MainProtocols/MVMCoreViewManagerViewControllerProtocol.h
index 70b8c4b..ff48b90 100644
--- a/MVMCore/MVMCore/MainProtocols/MVMCoreViewManagerViewControllerProtocol.h
+++ b/MVMCore/MVMCore/MainProtocols/MVMCoreViewManagerViewControllerProtocol.h
@@ -17,10 +17,10 @@
 @property (nullable, weak, nonatomic) UIViewController <MVMCoreViewManagerProtocol>*manager;
 
 // Notifies the view controller that it can be ready (usually means that it's committed to the screen).
-- (void)viewControllerReadyInManager:(nonnull NSObject <MVMCoreViewManagerProtocol>*)manager;
+- (void)viewControllerReadyInManager:(nonnull UIViewController <MVMCoreViewManagerProtocol>*)manager;
 
 // Notifies the current showing view controller that the manager is disappearing.
-- (void)managerWillDisappear:(nonnull NSObject <MVMCoreViewManagerProtocol>*)manager;
+- (void)managerWillDisappear:(nonnull UIViewController <MVMCoreViewManagerProtocol>*)manager;
 
 // Manager can check if the view controller does not want to be cached. You should be following proper caching techniques (caching, updating when needed, deleting when needed), so this should be a last resort.
 - (BOOL)shouldCacheInManager;