fix: App exit on back pressed

[GOVINDDIXIT]

fixes #626

GIF for the change

[GOVINDDIXIT]

@nikit19 pls review

[nikit19]

This is not the correct solution.
If the user is on the events fragment and he presses the back button, the app should close.
If he has opened search fragment he should return to the events fragment on backpress. (current behaviour)

[GOVINDDIXIT]

@nikit19 Updated and Added GIF for the changes. pls review

[iamareebjamal]

This is a workaround, find why super.onBackPressed is not working

[GOVINDDIXIT]

@iamareebjamal
As the Fragment lifecycle do not have onBackPressed(). So According to me alternative method to override onBackPressed() in Android 3.0 fragments can be done by creating an interface class OnBackPressedListener and Create class which implements skills of OnBackPressedListener and creating a listener and a method to set listener. But the current changes are also preforming same job. So I goes with it.

[iamareebjamal]

Fragments don't have onBackPressed, their container activity does. Find why it is not working

[GOVINDDIXIT]

@iamareebjamal @nikit19 pls review

[GOVINDDIXIT]

@iamareebjamal The problem is with the stack generated. Currently the onBackPressed method is loading the event fragment two times one with loadfragment and then with checkandLoad method. So I had cleared the stack generated everytime the user press the back button and located the user to Event Fragment which is required . Now the user can easily exit the app as there is only 1 fragment in the stack.

[GOVINDDIXIT]

@iamareebjamal I think the issue is solved pls review

[iamareebjamal]

This is still a workaround. I will see what can be done

[iamareebjamal]

Old and conflicting with the current logic