Re: [cocoaheadsau] Mysterious behaviour of MFMessageComposeViewController in iOS 6

[Peter Goldsmith]

You might want to give this a read, it's a blog post with some analysis of iOS 6 remote view controllers

http://oleb.net/blog/2012/10/remote-view-controllers-in-ios-6/

As to why it hangs I'm not sure. Are you checking if you can send messages?

canSendText

Returns a Boolean value indicating whether the current device is capable of sending text messages.

+ (BOOL)canSendText

Return Value

YES if the device can send text messages or NO if it cannot.

Discussion

Always call this method before attempting to present the message compose view controller. A device may be unable to send messages if it does not support text message or if it is not currently configured to send messages. This method applies only to the ability to send text messages. Sending multimedia messages with this class is not supported.

in iOS 5.0 or later, you should register as an observer of the MFMessageComposeViewControllerTextMessageAvailabilityDidChangeNotification notification to be notified of changes in the availability of sending text messages.

On Tue, Nov 27, 2012 at 6:43 PM, Giovanni <omn...@gmail.com> wrote:

My app presents a MFMessageComposeViewController modally. It was working perfectly fine in iOS 5 (both on the simulator and on the device). After I upgraded my iPhone to 6, it simply doesn’t work anymore. The app freezes for like 10 seconds, then this message appears in the debugger

"Remote compose controller timed out (YES)!"

And the modal view does not show up. I searched extensively on stackoverflow and on the web, and couldn’t find any solution. As a final resort, I downloaded and ran the sample code of apple, "MessageComposer" and, alas, even in apple code it does not work on iOS 6. I`m completely clueless and have spent hours on this... Any idea how can I fix this?

I am also displaying the MFMailComposeViewController, without any issues.

Thanks!

Niraj

--
You received this message because you are subscribed to the Google Groups "Australian Cocoaheads" group.
To view this discussion on the web visit https://groups.google.com/d/msg/cocoaheadsau/-/ZC2kMiAFDcIJ.
To post to this group, send email to cocoah...@googlegroups.com.
To unsubscribe from this group, send email to cocoaheadsau...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cocoaheadsau?hl=en.

[Nathan de Vries]

On 26 November 2012 23:43, Giovanni <omn...@gmail.com> wrote:

I downloaded and ran the sample code of apple, "MessageComposer" and, alas, even in apple code it does not work on iOS 6.

If the sample app isn't working, you should definitely file a bug report at http://bugreport.apple.com

—Nathan

[Sherman Lo]

This article might be useful, it outlines changes to sharing in iOS6 to use separate processes:

http://oleb.net/blog/2012/10/remote-view-controllers-in-ios-6/

Based off that article it appears the problem is your iPhone isn't starting the MessagesViewService  process properly. It might be worth checking the iPhone's console to see if there are any error messages relating to it.

On 28 November 2012 10:33, Giovanni <omn...@gmail.com> wrote:

Yes, I am checking for the possibility to send text with those methods before.

I have been playing more with it. I installed the app on my wife's iPhone 4S, running iOS 6, and it works fine.

So it is either an issue with iPhone 5 or with my iPhone...

On Tuesday, November 27, 2012 6:43:45 PM UTC+11, Giovanni wrote:

My app presents a MFMessageComposeViewController modally. It was working perfectly fine in iOS 5 (both on the simulator and on the device). After I upgraded my iPhone to 6, it simply doesn’t work anymore. The app freezes for like 10 seconds, then this message appears in the debugger

"Remote compose controller timed out (YES)!"

And the modal view does not show up. I searched extensively on stackoverflow and on the web, and couldn’t find any solution. As a final resort, I downloaded and ran the sample code of apple, "MessageComposer" and, alas, even in apple code it does not work on iOS 6. I`m completely clueless and have spent hours on this... Any idea how can I fix this?

I am also displaying the MFMailComposeViewController, without any issues.

Thanks!

Niraj

--
You received this message because you are subscribed to the Google Groups "Australian Cocoaheads" group.

To view this discussion on the web visit https://groups.google.com/d/msg/cocoaheadsau/-/KPWZNy5Ip4sJ.

[rickerbh]

Are you guys using iOS6 on iPhone 4 hardware, with custom fonts in your navigation controller? If so, it's a know issue with Apple. I've lodged a radar on that (very) specific case, with a sample project, and they've closed it as a duplicate.  But it wouldn't hurt to get another radar created.

From what I've seen, it appears that if you've used an app that has already instantiated the Mail or Message Compose VC then it *might* work fine. It's as if some sort of watchdog process kills the compose view for taking too long to appear - and using custom fonts seems to make it take a long time to appear, on old hardware. If it's been recently started/used, then some sort of caching seems to kick in, which is why it *might* work fine, sometimes.

H.

On Wednesday, May 15, 2013 6:59:36 AM UTC+10, David Hoan wrote:

I add exactly the same problem. My app was running fine? and then impossible to display the SMS controller.

I rebooted my iPhone and it works fine !

[Nathan de Vries]

What's the Radar #?

—Nathan

--

You received this message because you are subscribed to the Google Groups "Australian Cocoaheads" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cocoaheadsau...@googlegroups.com.

To post to this group, send email to cocoah...@googlegroups.com.

Visit this group at http://groups.google.com/group/cocoaheadsau?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[rickerbh]

I filed 13249999 and it was closed as a duplicate of 13195606.

H.

[Nathan de Vries]

On 27 May 2013 14:22, rickerbh <hamish....@gmail.com> wrote:

I filed 13249999 and it was closed as a duplicate of 13195606.

Excellent. Thanks for the report :-)

—Nathan