Skip to main content
Ollie Edge
Inspiring
April 8, 2013
Question

StageVideo Application Crash iOS - AIR 3.7

  • April 8, 2013
  • 2 replies
  • 1495 views

Hey Everyone,

Just upgraded all my projects from 3.6 to the latest 3.7 beta and I'm coming across issues with StageVideo on iOS which were not present in 3.6. I've looked everywhere for information about what may have been changed in 3.7 but nothing is noted in the release notes? Is there something I am missing?

Explanation:
Play a StageVideo (.mp4) on iPad 2,5 (6.1.2), when the video finishes the application crashes without any useful logs anywhere.

Further Details:

Here is some further information and a link to a test application I've put together.

- Flash Builder 4.7
- AIR 3.7 SDK (April 2, 2013)(overlayed on 3.6 SDK)

- Mac OS 10.8.2 development machine

- iPad Mini version 6.1.2 (10B146)

- Video Format: H.264 AAC 1024x768 Stereo 733KB

I've exported and uploaded a sample project (2MB) with the problem I've explained which includes a couple of very short videos:

http://neurocog.com.au/downloads/bugs/AdobeBugReport12.zip

I'm stumped!

Ollie.


This topic has been closed for replies.

2 replies

Adobe Employee
June 6, 2013

We are able to reproduce the issue and now we are investigating on it.

Thanks for reporting,

Nimit

Ollie Edge
Inspiring
April 8, 2013

I think I have found the problem AIR 3.7 SDK the onPlayStatus method which is a method used along with NetStream is called twice with a "NetStream.Play.Complete" param. In my case this results in an Application crash because the onPlayStatus method closes and disposes the NetStream, on the second time around it has a hissy fit.

I guess this is a bug?

chris.campbell
Legend
April 8, 2013

This sounds like it might be a bug.  I'll let the iOS team know so they can review it.  If you get a chance, could you open a bug report over at bugbase.adobe.com and post back with the bug number?

Thanks,

Chris

Ollie Edge
Inspiring
April 8, 2013

Sure thing, I'll post one tomorrow morning, meanwhile in case anyone else comes across this, I've just setup a flag to double-ly make sure that the onPlayStatus method doesn't get called twice as a work-around.