Authorization Failed

[Faro1980]

After login with the code on BMW CarData Authentication, I always get the following error: Authorization Failed. Failed to poll for tokens.
So the login is successful, but afterwards I get that error. (see screenshot)

What can I do?

[silvinnio]

Hi,
I got the same with version 1.0.13.
After installing the stable version 1.0.11 I get different error.
Please advise.
Thank you 😊

[

[bmi-vi]

Homey app version: 1.0.13 experimental.

I get the same error as the above posters when trying to add a device. The app log says:

Network error during token polling {"error":"Cannot read properties of undefined (reading 'toUpperCase')","stack":"TypeError: Cannot read properties of undefined (reading 'toUpperCase')\n at DeviceCodeAuthProvider.pollForTokens (/lib/auth/DeviceCodeAuthProvider.ts:301:23)\n at processTicksAndRejections (node:internal/process/task_queues:105:5)\n at BmwDriver.pollForAuthorizationAsync (/drivers/ConnectedDriver.ts:315:7)"}

[silvinnio]

Hi ,

Tried again but same issues.
I have uninstalled the app, created a new client in Car Data, cleared tokens, checked with both versions of the app.11 and 13...
Is there any way to fix this?

I have even tried what lsiddiquee said, to use two different devices for code login and adding the device in Homey and not to switch between the application or webpage but, still doesn't work.

,

[j0bro]

Same here, still the case with the 1.0.14 version of the app (May 1 2026)

[silvinnio]

Hi,
I can confirm that also with version1.0.14, I have the same issue too 😒

[lsiddiquee]

A test build (v1.0.15) is now available with a fix for the token-polling crash that produced the generic "Failed to poll for tokens" message. The token endpoint response is now parsed defensively, and error details from BMW are surfaced to the UI. Further improvements to the OAuth device-flow polling loop (slow_down handling, transient-error retry) are landing in the next build.

Please install from the Homey test channel and report back:

https://homey.app/en-nl/app/com.rexwel.bmwconnected/BMW--Mini-Connected/test/

[lsiddiquee]

Update: v1.0.16 has been submitted to the test channel with additional hardening of the device-code pairing flow on top of v1.0.15:

• slow_down from the OAuth server now correctly extends the polling interval (per RFC 8628 §3.5) instead of aborting the flow.
• Transient network errors during token polling are now retried instead of failing the whole authentication window.
• Container setup errors that occur after a successful login are now clearly labelled (Container setup failed: ...) so they're not misreported as "Authorization Failed".
• Stale poll loops from a retried pairing attempt no longer race with the new one.
• requestDeviceCode retries once on transient network failure.

Please try the test version once it's promoted: https://homey.app/en-nl/app/com.rexwel.bmwconnected/BMW--Mini-Connected/test/

If you still see the failure, please share the new logs — the additional logging in v1.0.16 should make the root cause much clearer.