The new version 1.65 is out and it got some extra testing for stopping the listening loop at sensitive moments in the audio setup. I couldn’t find any timings in the current version in which calling stopListening (which is how you prepare to respond to an interruption such as an incoming call or route change) could cause an exception. To the best of my knowledge, as long as you respond to interruptions with stopListening you should not encounter any exceptions as a result of incoming calls. I definitely could not cause any exceptions or crashes in 1.65 at any point in the loop for OpenEars or RapidEars during a route change, which has a very similar overhead in terms of causing immediate changes in the audio stream that require a fast shutdown of the loop so it can be restarted later.