[iOS]Bug: Unsaved choice/s for "Types" menu

[LyubomirShutilov]

video-1644526201.mp4

[z-zafirov]

I think this is not an issue, but happens due to system architecture specifics. Severity is low and fixing it might increase the battery and/or network consumption on the device, which is worst in that case, so my opinion is to close that ticket as "won't fix".

[BurningAXE]

Actually this is intentional - we want users to start by seeing all the signals and only filtering if this is problematic to find the one they are looking for. This way they won't forget a filter on and ignore some signal types.
It may not be what is expected by most users and it also may not be the best UX. I can see a point why starting with the last used filter may be expected.