We have an (non-scene) application which uses a splitViewController on iPad. We use a blocker view to obscure sensitive information when the application resigns active (i.e. double tap the home button/swipe up on devices with no home button).
This works great in general, but now we're moving on to supporting iPad Multitasking and there seems to be a "blocker view" created by the system when transitioning from collapsed -> expanded (showing a blur of sorts with the application icon in the center). Because appWillResignActive is also called when transitioning, we end up with a mishmash of both our own blocker view and the system's blocker view which doesn't look too great.
These are the splitViewController collapse/separate methods I'm referring to below:
My question is:
Is there someway to suppress the system's blocker view when transitioning to different iPad multitasking collapsed/expanded sizes?
If the answer to that is no, then is there some way to detect that the application is resigning active because of the transition?
What I've discovered so far:
- applicationWillResignActive is called prior to the splitViewController's collapse/separate methods
- The splitViewController's collapse/separate methods are called after the system's blocker view is displayed so it doesn't help to remove our own app's blocker view in those methods
- willTransitionToTraitCollection is also called after the system shows it's blocker view so it's too late to remove our own blocker view there as well
What I've tried:
- Move obscuring our sensitive data using the blocker view to applicationDidEnterBackground: << This is not ideal as it doesn't obscure the sensitive data when the user double taps the home button or swipes up which is the scenario we're trying to use the blocker view to obscure
- Change the blocker view to a VisualEffectView with blur << Again not ideal as it doesn't look great when obscuring the view and we're not transitioning
Thank you.