Normally when I see this sort of thing happening its caused by a wrapping
uinavigationcontroller ot uitabbarcontroller - check out so - there are lots
of questions like
http://stackoverflow.com/questions/3560669/viewwillappear-viewdidappear-not-being-called-not-firing
Stuart
--
View this message
yeah, maybe you could provide the code? gist.github.com
the MWC sample subclasses DialogViewController
https://github.com/xamarin/mobile-samples/blob/master/MWC/MWC.iOS/Screens/iPhone/UpdateManagerLoadingDialogViewController.cs
which is in turn subclassed
I have solved that problem by install ios xcode 4.3.1 for lion on snow
leopard as descripted here:
http://www.iphonedevsdk.com/forum/iphone-sdk-development/100229-snow-leopard-sdk-5-1-a.html
bye
--
View this message in context:
I've got an app that only 1 customer says is crashing at the same point
every time she uses it...However, I and my beta testers cannot reproduce it
at all...
Are there any techniques\libraries\computer gods to pray to that may give
me an idea? Are there logs on her phone she'd have access to?
I'd suggest embedding TestFlight into your app.
It's not a remote debugger but you will find it useful to track checkpoints
in your app, receive logging messages and report crashes. You could put
your trace messages in there and see the user's session logs appear on the
website.
