Fix issue - NewSiteCreationService can enter invalid state #9141
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.
Fixes #9138
This PR fixes a bug when NewSiteCreation service could enter an invalid state - the UI kept showing an infinite progress indicator.
This is happening when we start creating the site when we don't have an internet connection. The
NewSiteCreationService.createSite(..)
is not called since we check the internet availability before we call it. However, the service is created anyway when NewSiteCreationPreviewFragment binds to it in onResume. The default state of the service is IDLE, however this line prevents the service from actually starting the task when the user clicks on the retry button.The flow works as expected when the internet connection is available since the
NewSiteCreationService.createSite(..)
is invoked before the service is created and therefore the state of the service isnull
and notIDLE
.To test:
Update release notes:
RELEASE-NOTES.txt
.