Should I dismiss the MFMessageComposeViewController in the didFinishWithResult delegate method?

I'm trying to allow the user to send multiple text messages in a row in the MFMessageComposeViewController, but if I don't dismiss the controller in the didFinishWithResult delegate method, the Cancel button in the top right corner is disabled and the user has no way to exit the text message interface.

Is MFMessageComposeViewController only for sending one-time messages?

func messageComposeViewController(controller: MFMessageComposeViewController!, didFinishWithResult result: MessageComposeResult) {
  if result.value == MessageComposeResultCancelled.value {
    self.dismissViewControllerAnimated(true, completion: nil)
  }
}

      

Thanks for the help.

+3
ios swift mfmessagecomposeview


source to share


No one has answered this question yet

See similar questions:

0
Don't want to dismiss the MFMessageComposerViewController after posting the message?

or similar:

3
Mfmessagecomposeviewcontroller quits immediately after showing
2
How can I include the camera in the MFMessageComposeViewController?
2
Get list of body and recipients of messages from MFMessageComposeViewController
1
IOS delegate in native extension
0
Error presenting AlertView while rejecting MFMessageController
0
Is there a way to access the list of conversation groups in the MFMessageComposeViewController?
0
Reject UITableView Cell after selection in Swift?
0
MessageComposeViewController does not call delegate
0
Don't want to dismiss the MFMessageComposerViewController after posting the message?
-1
MFMessageComposer cancel button not showing in iOS 11



All Articles
Loading...
X
Show
Funny
Dev
Pics