• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

Problems with Sound & IOS/Air4SDK(1/28/14 version)

Explorer ,
Feb 11, 2014 Feb 11, 2014

Copy link to clipboard

Copied

We are trying to deploy an updated version of our app to the IOS app store. So we were told(from another post) to use the latest sdk4 beta, which we are in the process of testing our app with it. This is an existing deployed app simply re-compiled w the latest air4 beta sdk.

If we  play an mp3 sound file in the foreground, then pause the audio, then place the app in the background for 2-4 minutes, then bring the app back into the foreground and start playing again, there is no audio, although the sound object still updates with progress events real fast, showing the track playing at a rapid pace.

Then, If we load a different track, still no audio at first (and no progress events either), but after some time, maybe a minute or two, the audio starts.

This happens on IOS7 as well as previous IOS versions on various IOS devices with this SDK.

This doesent happen with previous SDK versions.

Yes, its a bit screwy.

Dear Adobe- we need to get our app into the app store, AFAIK, there is currently no way to get an AIr app into the IOS app store - or am I wrong?

Thanks,

Bob

TOPICS
Performance issues

Views

731

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Feb 11, 2014 Feb 11, 2014

Copy link to clipboard

Copied

Hello,

Could you please share the sample application with app.xml, this will help us reproduce the problem. Also, share the AIR SDK version into which application was working fine with devices name, OS. If you'd like to keep this private, feel free to email the sample application to me directly @ nimitja@adobedotcom

Thanks for reporting,

Nimit

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Feb 13, 2014 Feb 13, 2014

Copy link to clipboard

Copied

Here is an update and additional info on this apparent ios related bug:

Once the app is brought back to the foreground, and you start playing the audio, there is no audio for several minutes, but then the audio comes starts after several minutes - during the no audio period, there are still progress events and the audio position is increasing( but about twice the normal rate).

Also, if after bringing the app back into the foreground we close the current audio and open another mp3 file, we get the same no audio problem with the audio coming back after several minutes.

Our deployed IOS app store app is on Air SDK 3.7 and does not have the problem.

We tested our latest build on SDK4.0 (1390), 4.0 (1619), 3.9(1619), all exhibit the problem, we re-tested with Air 3.7 and the problem does not exist.

The symtoms are the same on various ios versions and devices. We tested on: IOS 7.0.4 with Iphone 5, IOS 6.1.3 with iPhone 3GS.

The problem does not seem to exist on Android(testing the latest SDK 4.0 and android 4.3.1).

I will try to make a sample app to demo the problem and get it to you today.

Thanks,

Kelly

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Feb 13, 2014 Feb 13, 2014

Copy link to clipboard

Copied

Update:

I did discover, while making a simple test app  that the problem only exists when  

NativeApplication.nativeApplication.executeInBackground = true; on app deactivate.

The problem doesent exist if its not set on deactivate.

Unfortunately we need to save our app state and send out some info before the app deactivated and need executeInBackground = true. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Feb 13, 2014 Feb 13, 2014

Copy link to clipboard

Copied

Thanks for the investigation, plesae share the sample application including application.xml.

Regards,

Nimit

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Feb 14, 2014 Feb 14, 2014

Copy link to clipboard

Copied

LATEST

Another update:

There seems to be a workaround:

If the last thing we do after executing all  additional background tasks we have, after app deactivate event, but before the app actually deactivates is to  set NativeApplication.nativeApplication.executeInBackground  back to false, then the bug does not occur.

This is a ridiculous hack, but it *seems* to work for now.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines