Remove super.onReceive from our 3 widgets. #517
Merged
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
Coverage Report (Type: Instructions)
|
JohnFrontzos
approved these changes
Feb 19, 2025
PavlosTze
deleted the
feature/fe-1616-fix-weird-empty-states-on-widgets
branch
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.
Why?
There were some weird cases of widgets getting in an "empty"/undefined state in some cases (e.g. when clearing cache + data of the app). In this PR we are fixing this.
How?
Remove
super.onReceivefrom our 3 widgets so all the updates in our code take place through our custom overrides inonReceive.Testing
Check the states of a widget(s) and ensure everything is OK, e.g.: