Fix config flow when cookies file expires #32
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
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.
When a cookies file expires, this creates a repair issue requiring the config entry to be reconfigured. However, when the (reauth) config flow is started, an error results stating the config flow cannot be loaded (internal error 500.) This is due to the way the reauth flow works, which the code did not handle properly. This change fixes that problem by saving the cookies file path (cf_path) for the
async_step_old_cookies_invalidmethod.Fixes #28. Note, this only fixes the reauth config flow. It does not address the reason the cookies file is expiring in the first place.