I disabled airsense after the latest updates. It still alerted me to the presence of an aircraft (I could hear one). Seems the opposite of what other people are seeing...
edit - try turning it off in app and see if you get it working. Perhaps the code has been somewhat erroneously 180'd.
Whoah... possible coding bug, and testing fail.
This is so easy to do. In some of the most popular coding languages, these two lines of pseudo-code test, and then execute on opposite conditions:
IF (AIRSENSETOGGLE) THEN do stuff
vs.
IF (!AIRSENSETOGGLE) THEN don't do stuff
The difference is the "!". When evolving code, it's not unusual to, for some design reason, to change the sense of a test, rewrite the code to be executed if true for the opposite sense.
If you forget to change the condition and reverse it with a ! (logical NOT), the new release would work as described here.
Not saying I know in any way that this is what's going on, here, giving an example of how easy it is to make an error like this..
UI testing should catch this.