Skip to content
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

Oauth credentials screen doesn't show up #23429

Closed
4 tasks done
joostlek opened this issue Dec 24, 2024 · 2 comments · Fixed by #23440
Closed
4 tasks done

Oauth credentials screen doesn't show up #23429

joostlek opened this issue Dec 24, 2024 · 2 comments · Fixed by #23440
Milestone

Comments

@joostlek
Copy link
Member

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

So when adding an integration that requires oauth credentials (fitbit/withings/spotify/husqvarna), the popup to add my application credentials does not show up after the popup that loads the config flow dissapears. It only shows up after I started another config flow (not necessarily with oauth).
image

Describe the behavior you expected

I would expect the oauth credentials popup to come up immediately

Steps to reproduce the issue

  1. Start a config flow for Husqvarna
  2. See the spinner pop up dissapear
  3. See the nothingness
  4. Start a new flow for accuweather
  5. Now see the husqvarna application credentials popup
  6. profit

What version of Home Assistant Core has the issue?

2025.1.0b0

What was the last working version of Home Assistant Core?

2024.12 also has this issue

In which browser are you experiencing the issue with?

Firefox 133

Which operating system are you using to run this browser?

macOS something

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

@joostlek
Copy link
Member Author

Okay this is strange, I tried looking for any logs during this moment, but I could not replicate it afterwards.

Yesterday a friend of mine discovered this bug on a brand new system. And the first time today I could replicate it. But I can't anymore. :/

@bramkragten bramkragten added this to the 2025.1 milestone Dec 24, 2024
@bramkragten
Copy link
Member

Yeah it is a race condition...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants