In the VFR charts, when I tap an airspace boundary which is dividing multiple airspaces (e.g. the arc or line representing an altitude step in Class B airspace), the app becomes unresponsive to any further input and needs to be closed and reopened.
This has been tested on a Pixel 8 Pro running Android 16 CP1A.260405.005, with Charts version 8.43.1 (build DB95B8AC8). The issue only happens in the app; the web version is fine in both Firefox and Chrome (though suboptimal).
The menu appears to display for up to a frame before vanishing (sometimes it doesn’t appear, sometimes it briefly flickers into existence). Tapping in the area the menu appears does not appear to result in anything happening; the menu does not appear to be interactable in this situation. I am unable to determine if the menu is being moved behind the map (e.g. due to a z-order issue) or just being made hidden for whatever reason.
While I did not test removal and reinstallation of the app (as it is unlikely to have an effect beyond what I’ve tested), clearing the app storage (including cache) does not have any effect on if the bug occurs.
It looks like this issue might have been reported a year ago on a different Android device ( Freeze when click airspace ), but it was marked as closed without actually resolving the app’s issue (the “resolution” was to use the web version).
Thanks a lot for the report. Would it be possible for you to upload a video of the behavior, please, that would be very helpful.
Regarding uninstalling/reinstalling, typically this can be the most effective means to fix issues like you describe. Clearing cache will only remove that saved data and not a botched app update.
Due to forum file size limits and my not being home to run the recording through ffmpeg to cut down on the size, attached is a very abridged recording of the issue (with the Android developer option showing input), demonstrating the minimal reproduction steps on my end. Not shown in the video (due to file size limits) is additional flailing about the screen after the lockup, including a demonstration that tapping either where the window flickered or on the bottom bar has no effect.
I was just able to also reproduce it on my old phone (Pixel 5, Android 14 UP1A.231105.001), with the exact same behavior.
I was just doing some more testing on my 8, and my current theory is that the airspace selection menu is getting put in a spot off the right or bottom edge of the screen, and since it’s modal, it’s blocking input to the rest of the app. See what happens if the airspace border you’re selecting is at the bottom right corner of the screen. The positioning of the menu appears to be a divergence in the Android app compared to the web version, as it seems to always get placed in a reasonable spot on the web, while Android is putting it far away (see screenshot, which is using the same developer option for showing input).
A small related issue I’ve noticed in testing for this one is that the “back” Android action isn’t doing anything when the selection menu is open; in theory, it should cancel selecting an airspace, which would mean I could do the “back” gesture after bug reproduction to allow the rest of the app to continue to function.
