iPhone iOS 4.0 Camera FigCreateCGImageFromJPEG returned -1

Question

Hi, Since I updated to 4.0, when I take a photo with my App using UIImagePickerController I get the following error output:

* ERROR: FigCreateCGImageFromJPEG returned -1. Input (null) was 711733 bytes.

I still get the image returned and can continue as normal, but does any body know what and why I get this error. I also get the following warnings that could be related:

Using two-stage rotation animation. To use the smoother single-stage animation, this >application must remove two-stage method implementations.

Using two-stage rotation animation is not supported when rotating more than one view >controller or view controllers not the window delegate

Any information would be of great help. Thanks in advance.

Cheers

Al

Answer 1

You might want to first try the search on stackoverflow.com before posting :) There's a 5 months old answer to that : http://stackoverflow.com/questions/2048781/single-stage-vs-two-stage-animation-for-iphone-apps

Answer 2

I also have problems with UIImagePickerController on iOS 4.0, It works on simulator on 3.0 but on 4.0 i have a crash the delegate method - (void)imagePickerController:(UIImagePickerController *)picker didFinishPickingMediaWithInfo:(NSDictionary *)info is called twice, and if i build on the phone and use camera it works ok.

Answer 3

Alan, did you resolve the issue with didFinishPickingMediaWithInfo being called twice? I'm experiencing the same thing in my app. I've tracked it down to showing a UIProgressView that I pop up over the UIImagePickerController UI while I do some processing in a second thread. I don't (and don't want to) dismiss the UIImagePickerController while I process the image. This didn't happen in 3.0 and doesn't happen on the 4.0 Simulator, only 4.0 device.

Answer 4

Regarding the error - have a look here

Answer 5

Yeah, I'm getting it as well. I also haven't found any real solution for it yet. I've tried just about everything I can think of and I'm getting some EXC_BAD_ACCESS right after it which I'm sure it probably related, but if anyone has found out more about this error, it sure would be nice to get a resolution to it.