When deleting a filter, the tracks event for the Filters screen (filter_list_shown) that is immediately shown does not accurately reflect the deletion of the filter. Specifically, the count is what you would expect if you had not deleted a filter.
Create a new filter
Return to Filters screen
Observe the filter count logged in Tracks: 🔵 Tracked: filter_list_shown, Properties: {"filter_count":[N],..
Tap on the new filter
Delete the new filter using the overflow menu
🔴 Observe that when you are returned to the Filters screen the same filter count is logged even though there is now one less filter.
This appears to be because of a race condition between the loading of the view and the update of the filter list from the repo. In my testing the filter list comes in about 50ms after the view is loaded.
When deleting a filter, the tracks event for the Filters screen (
filter_list_shown
) that is immediately shown does not accurately reflect the deletion of the filter. Specifically, the count is what you would expect if you had not deleted a filter.🔵 Tracked: filter_list_shown, Properties: {"filter_count":[N],..
h/t to @ashiagr for identifying this.