The FxA signing out process offers the user the possibility of clearing out the bookmarks, history and logins store. This logic is implemented by deleting directly the sqlite files that contain the databse for such user data. This file is created during the app startup process and there is no way to do it without a restart.
The main goal of this PR is to ensure the signout procedure doesn't clear the storage without proceeding with the restart, so that we avoid the inconsistent state described on the issue #1307. Hence, we are going to launch a confirmation dialog to ensure the user is willing to proceed with the restart, going back to the sign-out dialog otherwise so that the user uncheck the option to clearing up the storage or even cancel the signout process altogether.
The FxA signing out process offers the user the possibility of clearing out the bookmarks, history and logins store. This logic is implemented by deleting directly the sqlite files that contain the databse for such user data. This file is created during the app startup process and there is no way to do it without a restart.
The main goal of this PR is to ensure the signout procedure doesn't clear the storage without proceeding with the restart, so that we avoid the inconsistent state described on the issue #1307. Hence, we are going to launch a confirmation dialog to ensure the user is willing to proceed with the restart, going back to the sign-out dialog otherwise so that the user uncheck the option to clearing up the storage or even cancel the signout process altogether.
Fixes #1307