Refactored the OpenSettingsDialogFragment class to have an empty constructor.
According to the Android documentation, every Fragment class should have an empty constructor that does nothing and is not a non-empty constructor. [Reference](https://developer.android.com/reference/android/app/Fragment.html#Fragment()). Not doing this leads to the Android ecosystem being unable to restore the Fragment's state when re-instantiated causing the issue mentioned in the linked issue.
Testing:
For e2e testing, you can start using the app normally and ensure that it does not crash and to test the functionality that the OpenSettingsDialogFragment class provides, you can tap the screen 5 times and then, right-swipe the screen with 2 fingers.
Fixes: #338
Refactored the
OpenSettingsDialogFragmentclass to have an empty constructor. According to the Android documentation, everyFragmentclass should have an empty constructor that does nothing and is not a non-empty constructor. [Reference](https://developer.android.com/reference/android/app/Fragment.html#Fragment()). Not doing this leads to the Android ecosystem being unable to restore the Fragment's state when re-instantiated causing the issue mentioned in the linked issue.Testing: For e2e testing, you can start using the app normally and ensure that it does not crash and to test the functionality that the
OpenSettingsDialogFragmentclass provides, you can tap the screen 5 times and then, right-swipe the screen with 2 fingers.