SPatrickB

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)

  • Author
    Posts
  • in reply to: [Resolved] App rejected #1019950
    SPatrickB
    Participant

    There was only the one reference to an audio session in my code which was the call to setSoundMixing.

    in reply to: [Resolved] App rejected #1019947
    SPatrickB
    Participant

    I can confirm that removing the call to setSoundMixing (from my controller init) has stopped the mic consent and has not affected the AudioServicesPlaySystemSound operation either.
    Still, I do not understand why this was happening.

    in reply to: [Resolved] App rejected #1019945
    SPatrickB
    Participant

    Ah, I am using AudioServicesPlaySystemSound elsewhere in my app and am therefore calling [[AudioSessionManager sharedAudioSessionManager] setSoundMixing:true];

    in reply to: [Resolved] App rejected #1019943
    SPatrickB
    Participant

    I can see in my app that audioSessionHasBeenInstantiated is never set to TRUE in initial or subsequent calls to the say method. Is this pertinent?

    in reply to: [Resolved] App rejected #1019938
    SPatrickB
    Participant

    OK, settings->general->reset->reset location & privacy will remove the previous settings, i.e. no need for bundle ID change.
    However, after setting the noAudioSessionOverrides to TRUE, it appears to only work for the initial call to the say method. I still have the microphone consent request popping up with subsequent calls even though the noAudioSessionOverrides flag is still set to TRUE;

    in reply to: [Resolved] App rejected #1019802
    SPatrickB
    Participant

    Changing the bundle ID worked, thanks.

    in reply to: [Resolved] App rejected #1019790
    SPatrickB
    Participant

    When I delete the app and reboot the device, I see that it has also gone from the settings but when I reinstall, it reappears in settings also. I don’t know what else I can do.

    in reply to: [Resolved] App rejected #1019752
    SPatrickB
    Participant

    I set that flag but I still see an entry for my app appearing in settings/privacy/microphone. However, it’s OK, I’ll just wait out until the next version of OpenEars.

    in reply to: [Resolved] App rejected #1019546
    SPatrickB
    Participant

    My app update (for iOS 7) just got rejected for the exact same reason given by Apple. Trouble is my app is only using TTS and so should not use the microphone.
    If a flag could be set in the API for TTS only (use AVAudioSessionCategoryPlayback) then I think this could be resolved.

Viewing 9 posts - 1 through 9 (of 9 total)