Clarify FCM SDK swizzling notice (#291)

The previous message was worded in a way as to imply that the FIRAppDelegateProxyEnabled key **should** be set to NO, disabling swizzling. This clarifies that message, indicating that this is for developers who would prefer to manually integrate the SDK.

1 files changed, 8 insertions, 3 deletions

diff --git a/Firebase/Messaging/FIRMessaging+FIRApp.m b/Firebase/Messaging/FIRMessaging+FIRApp.m
index 50078bf..30f96af 100644
--- a/Firebase/Messaging/FIRMessaging+FIRApp.m
+++ b/Firebase/Messaging/FIRMessaging+FIRApp.m
@@ -75,11 +75,16 @@
 
   // Swizzle remote-notification-related methods (app delegate and UNUserNotificationCenter)
   if ([FIRMessagingRemoteNotificationsProxy canSwizzleMethods]) {
+    NSString *docsURLString = @"https://firebase.google.com/docs/cloud-messaging/ios/client"
+                              @"#method_swizzling_in_firebase_messaging";
     FIRMessagingLoggerNotice(kFIRMessagingMessageCodeFIRApp000,
                              @"FIRMessaging Remote Notifications proxy enabled, will swizzle "
-                             @"remote notification receiver handlers. Add \"%@\" to your "
-                             @"Info.plist and set it to NO",
-                             kFIRMessagingRemoteNotificationsProxyEnabledInfoPlistKey);
+                             @"remote notification receiver handlers. If you'd prefer to manually "
+                             @"integrate Firebase Messaging, add \"%@\" to your Info.plist, "
+                             @"and set it to NO. Follow the instructions at:\n%@\nto ensure "
+                             @"proper integration.",
+                             kFIRMessagingRemoteNotificationsProxyEnabledInfoPlistKey,
+                             docsURLString);
     [FIRMessagingRemoteNotificationsProxy swizzleMethods];
   }
 }