Actually, I was mistaken. When I receive the InterAppConnected
property change notification I do in fact stop the session, then start
it again immediately. But everything seems fine after that on my end.
The only other potential trick I use, is a test in my audio engine start
code path (before the actual session activate call) similar to the following:
====
UIApplicationState appstate = [UIApplication
sharedApplication].applicationState;
bool inForeground = (appstate != UIApplicationStateBackground);
if (!inForeground && !mInterAppConnected) {
// Start called in background, maybe need to wait for inter app
audio connection
return;
}
=====
This could occur only when the app was started in the background by an
IAA host and we haven't received the connected notification, and
defers actual starting of the audio session until we receive the
InterAppAudioConnected property change notification (at which time
we'll start the session).
jlc
>> > email to
open-music-app-colla...@googlegroups.com.
> --
> You received this message because you are subscribed to the Google Groups
> "Open Music App Collaboration" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
open-music-app-colla...@googlegroups.com.