Bug 2955 - AudioSession::SetActive (false) throws an exception if it is not active
Summary: AudioSession::SetActive (false) throws an exception if it is not active
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 5.0
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-01-18 11:17 UTC by Jackson Harper
Modified: 2013-12-05 18:36 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Jackson Harper 2012-01-18 11:17:38 UTC
iOS returns a non-zero error here (session not active), but this probably isn't worth throwing an exception over.
Comment 1 Sebastien Pouliot 2012-01-20 22:40:26 UTC
Calling this twice did not result in an exception (from an error code).

			AudioSession.SetActive (false);
			AudioSession.SetActive (false);

I suspect the error comes only if other things where done before - but it's not as easy as

			AudioSession.SetActive (true);
			AudioSession.SetActive (false);
			AudioSession.SetActive (false);

Can you get me a test case and/or the exact error number that should be ignored / not converted into an exception. Thanks
Comment 2 Jackson Harper 2012-01-20 22:45:20 UTC
Doubt I'll have time to put together a test case, I do know its NotActiveError ('!act') though.
Comment 3 PJ 2013-11-19 17:05:45 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 4 PJ 2013-12-05 18:36:12 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.