MonoDevelop might simply be trying to run an already compiled version of the app You might be trying to deploy the app to an iphone using a certificate that is expired. In that case, go to iTunes connect and get a new one.
MonoDevelop might simply be trying to run an already compiled version of the app. You might be trying to deploy the app to an iphone using a certificate that is expired.In that case, go to iTunes connect and get a new one.
I did try cleaning the solution (multiple times). I also checked the expiration dates of the certificates in XCode. None of them expire for another three months.
The app builds and installs just fine in Debug or Release mode, just not Distribution. – Rob Gibbens Feb 26 at 19:01 oh, you're trying to run the distribution build? You can't do that.
The signature that apple provides you to send the build to their appstore doesn't allow you to run the executable in a phone. Only after they resign it that it runs.. Hopefully that's it. – Eduardo Scoz Feb 26 at 22:39 Oh geez...this is what I get for leaving iOS development for a couple of months.
That makes sense, thanks. – Rob Gibbens Feb 27 at 4:07.
I'm revisiting some MonoTouch code that I wrote a few months ago and haven't touched since then. This is was working fine and is deployed to the App Store. When I open it now and try to Run it in Distribution|iPhone mode, I get the error "The application was terminated by a signal: SIGIOT".
The other thing that I noticed is that under Properties->iPhone Build, my SDK version was set to "3.2 (not installed)". I switched this to 4.2 (the only other choice), but it dind't help.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.