No, it sounds like overlogging from deep within the AVAudioSession implementation, even down to referencing a line number inside of a C++ implementation file whose corresponding interface is private. If everything works as defined from OpenEars’ API it would be questionable to troubleshoot an implementation detail we have no access to or documentation about, for qualities (port validation) we’ve never heard of.