-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(#376): fix issue of the app crashing in some phones #377
Open
sugat009
wants to merge
5
commits into
master
Choose a base branch
from
376-google-reporting-app-crashes-on-some-phones
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
126e65f
fix(#376): fix issue of OpenSettingsDialogFragment class not being ab…
sugat009 bef1287
Remove unused import
sugat009 cc2815a
fix unit tests
sugat009 c294f6e
Fix sonarlint issue
sugat009 46abd6c
Add unit tests for view setup in OpenSettingsDialogFragment
sugat009 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, I am probably missing something here, but in my testing, adding this line here in the
onCreate
was all that I needed to avoid the error in question.In my debugging it seemed like without this line, the
OpenSettingsDialogFragment.onCreate
method was getting called a bunch of times when entering/exiting split-screen mode before theEmbeddedBrowserActivity.onCreate
method is even called. When this happened, thewbvMain
view was still null (presumably because the activity was not created yet). Eventually, theEmbeddedBrowserActivity.onCreate
method is called for the new activity and that triggers theOpenSettingsDialogFragment.onCreate
method to be called again (and this time thewbvMain
view exists.However, if I set
setRetainInstance(true);
here inOpenSettingsDialogFragment.onCreate
and leave everything else as it is inmaster
, it prevents all the extra initial calls toEmbeddedBrowserActivity.onCreate
that were happening beforeEmbeddedBrowserActivity.onCreate
and so avoids the error. When theEmbeddedBrowserActivity.onCreate
function is called, that triggers a call toOpenSettingsDialogFragment.onCreate
which then can access thewbvMain
view at that point in the lifecycle.I am not 100% sure about exactly what is happening here. The
EmbeddedBrowserActivity.onCreate
is not getting called multiple times. My theory is that there is some weird connection between the activity lifecycle and the fragment lifecycle that is causing theOpenSettingsDialogFragment.onCreate
function to get called at other points during the activity lifecycle as the originalEmbeddedBrowserActivity
is destroyed. SettingsetRetainInstance
seems to decouple the fragment from the activity lifecycle so that this does not happen.