@@ -57,23 +57,6 @@ typedef void(^FIRMessagingDeleteFCMTokenCompletion)(NSError * _Nullable error)
5757 */
5858typedef void (^FIRMessagingTopicOperationCompletion)(NSError *_Nullable error);
5959
60- /* *
61- * The completion handler invoked once the data connection with FIRMessaging is
62- * established. The data connection is used to send a continuous stream of
63- * data and all the FIRMessaging data notifications arrive through this connection.
64- * Once the connection is established we invoke the callback with `nil` error.
65- * Correspondingly if we get an error while trying to establish a connection
66- * we invoke the handler with an appropriate error object and do an
67- * exponential backoff to try and connect again unless successful.
68- *
69- * @param error The error object if any describing why the data connection
70- * to FIRMessaging failed.
71- */
72- typedef void (^FIRMessagingConnectCompletion)(NSError * __nullable error)
73- NS_SWIFT_NAME(MessagingConnectCompletion)
74- __deprecated_msg(" Please listen for the FIRMessagingConnectionStateChangedNotification "
75- " NSNotification instead." );
76-
7760#if defined(__IPHONE_10_0) && __IPHONE_OS_VERSION_MAX_ALLOWED >= __IPHONE_10_0
7861/* *
7962 * Notification sent when the upstream message has been delivered
@@ -426,36 +409,6 @@ NS_SWIFT_NAME(Messaging)
426409 completion:(FIRMessagingDeleteFCMTokenCompletion)completion
427410 NS_SWIFT_NAME (deleteFCMToken(forSenderID:completion:));
428411
429-
430- #pragma mark - FCM Direct Channel
431-
432- /* *
433- * Create a FIRMessaging data connection which will be used to send the data notifications
434- * sent by your server. It will also be used to send ACKS and other messages based
435- * on the FIRMessaging ACKS and other messages based on the FIRMessaging protocol.
436- *
437- *
438- * @param handler The handler to be invoked once the connection is established.
439- * If the connection fails we invoke the handler with an
440- * appropriate error code letting you know why it failed. At
441- * the same time, FIRMessaging performs exponential backoff to retry
442- * establishing a connection and invoke the handler when successful.
443- */
444- - (void )connectWithCompletion:(FIRMessagingConnectCompletion)handler
445- NS_SWIFT_NAME (connect(handler:))
446- __deprecated_msg(" Please use the shouldEstablishDirectChannel property instead." );
447-
448- /* *
449- * Disconnect the current FIRMessaging data connection. This stops any attempts to
450- * connect to FIRMessaging. Calling this on an already disconnected client is a no-op.
451- *
452- * Call this before `teardown` when your app is going to the background.
453- * Since the FIRMessaging connection won't be allowed to live when in the background, it is
454- * prudent to close the connection.
455- */
456- - (void )disconnect
457- __deprecated_msg (" Please use the shouldEstablishDirectChannel property instead." );
458-
459412#pragma mark - Topics
460413
461414/* *
0 commit comments