Fix issue caused by duplicated main adapters causing crash: #598
Conversation
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
Issue: First adapter is created which creates all the fragments. Dining fragment spawns new thread for network request. Then, startHomeFragment() is called in MainActivity, which creates a new adapter and destroys the old one. Then, the dining network request finishes and tries to access a null binding causing crash. Added Crashyltics error logging for when this happens but prevents crash on the User side.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue: First adapter is created which creates all the fragments. Dining fragment spawns new thread for network request. Then, startHomeFragment() is called in MainActivity, which creates a new adapter and destroys the old one. Then, the dining network request finishes and tries to access a null binding causing crash.
Added Crashyltics error logging for when this happens but prevents crash on the User side.