Inspiring

Answered

iOS app crashes on return from cameraUI - a memory allocation problem?

Forum|Forum|14 years ago
November 24, 2011
25 replies
22772 views

hey all

trying to finish my first app

when running on iOS, the app SOMETIMES crashes after returning from cameraUI (either "use"/MediaEvent.COMPLETE or "cancel"/Event.CANCEL).

when i exit some other running apps on my iPhone 3Gs (and not that many are open), the problem goes away, which makes me think this is some memory allocation problem

in that aspect, can i trust the iOS to exit inactive applications to allocate more memory for my, currently active, AIR app?

(there is no memory leak)

this is an iPhone 3Gs running os version 4.3.5

the app was made with Flash Pro 5.5 overlayed with the AIR 3.1 sdk, and deployed using the "deploy for app store" type (which should be the most bug-free)

(no crashes on Android or desktop versions)

anyone had this cameraUI problem or a similar one where an app crashes if more then some numbers of apps are open?

thanx

Saar

This topic has been closed for replies.

Correct answer sanika Kulshreshtha

Hi,

Thanks for reporting the bug. This issue is known to us and it is currently under investigation. As far as I know, there is no workaround.

Regards,

Sanika

Show previous replies

A

Andy_____

Participating Frequently

Ditto here. Same problem, crashes Andorid HTC Desire phone when returning from taking picture. We are using the 'How to Use CameraUI in a Cross Platform Way' method (http://blogs.adobe.com/cantrell/archives/2011/02/how-to-use-cameraui-in-a-cross-platform-way.html ) but still fails.

I second the comments above: it needs to be fixed ASAP as without the camera functionality our suite of apps becomes worthless and we have to ditch and start again on another platform.

Please - when can we expect the update?

M

Marijn83

Participating Frequently

I have the same issue on Android. Anyone else have this aswell?

A

Andy_____

Participating Frequently

Yes, shelling out to the CameraRoll and CameraUI sometimes crashes the program on an Android HTC phone. We have only seen this happen on phones here, our Android Samsung Galaxy tablets seem okay with it. Using ANY of the described methods of calling the CameraUI will crash our Android phones after a couple of attempts (if not every time).

So it is definitely an issue with Android as well as iOS, and something of a dealbreaker for us.

Still waiting for an update on when the next release will be out please, if anyone at Adobe is reading this!

Here's hoping so anyway.

thanks

Andy

L

louisgates

Participant

Sanika, any update on this? We're seeing the same crashing behavior using the camera. We'd like to stick with flex mobile but this truly is a showstopper for us since we're planning a release very soon. Please restore our belief in flex mobile and provide us all with an update.

Thank you very much.

Louis

S

shanlyticketsolve

Inspiring

I don't get this. Its beyond frustrating:

we are not talking about using an uncommon phone capability, access to a phones camera is about the most basic native level of access you would be looking for in a mobile framework
we are not talking about an edge case in usage, just trying to take a simple picture consistently
we are not talking about a feature issue where it doesn't quite work the way you want, it crashes the whole app hard!
we are not talking about a hard to recreate, only happening to a few people case - it seems from what I have read the Camera integration is fundamentally broken and I have spent days researching this and only found frustration from people out there
we are not talking about an issue that does not have consequences - in several places on this forum and others people have emphasized how it is affecting their platform decisions, ability to submit apps. You even have people on this board recommending that not to use Flex Mobile and move to other platforms. Not what you want to be happening to when you are at the adoption phase of a new product.

And that is the response - on this thread and here http://forums.adobe.com/message/4125590#4125590 - we know its an issue but we don't know when it will be fixed and no proactive communication on status - only a growing body of people like me getting increasingly frustrated. What does it take for an issue to be a show stopper? priority 1? affecting customer decisions priority?

In my case I am in place where I am trying to make a platform decision and since this experience has happened I have subscribed to the live feed for this forum and as many relevant Adoble blogs, news feed etc. as I could find. I did this to get a feel for how well Adobe is supporting the mobile development on the AIR platform. Something increasingly important given recent decisions.

My perception so far is quite poor especially for a recently released product, i.e. 4.6 release. In fact the release that finally addresses performance enough to make AIR mobile development a risk free decision. You would expect Adobe to be all over the boards like this - with core developers, platform experts contributing actively. My perception, rightly or wrongly, is of a community trying to support itself without much help, or clear communication from Adobe. In fact if you look at the the articles coming out of Adobe recently its all phonegap, html5 etc. It does not fill you with confidence for the future.

To be clear - I have had a great experience with actionscript, flex etc and as a company we have developed the backend portion of our platform solely on Flex. I don't believe that we could have done it any other way and even now when I look at the alternatives for web development I feel vindicated in our decision.

However, this rant is caused by a genuine frustration and fear. I don't expect this to get a meaningful response but maybe if there are enough voices it will create an overall improvement.

Sean

S

sanika Kulshreshtha

Participating Frequently

@louisgates,@shanlyticketsolve

I have an update for you. We have fixed the issue in our internal builds and it should make it to the next release of AIR.

Thanks,

Sanika

S

shanlyticketsolve

Inspiring

I am about to make the same decision - probablt phonegap. I've spent days trying to get stability - even wrote an ANE to make converting to jpeg quicker to make performance acceptable for my use case. But the inability to get some stability from the CameraUI and silence on the issue is really frustrating,

I've been trying to use the prototype I am working on to advocate building our mobile applications on Flex mobile but this is killing it.

Sean

S

shanlyticketsolve

Inspiring

Is it possible to get an update on this - or even some guidelines on how to minimize crashes.

I also have an app submission been delayed by this.

Sean