Logged-in users: Airport detail shows “Unknown error”, METAR request hangs (pending), then timeline disappears; console TypeError in effects.js (v48.1.1, Rain overlay)

kerryeva

Hi Windy team,
I’m reporting a reproducible issue on desktop where the airport detail panel fails for logged-in users and can also make the timeline disappear.
Environment
Platform: Desktop (macOS)
Browsers tested: Safari and Chrome (same behavior). Also reproduced on another PC with Edge.
Windy version: 48.1.1 (from error report / request param v=48.1.1)
Overlay: Rain / Thunderstorm (overlay: "rain")
Summary of the problem
When logged in, clicking an airport opens the right-side detail panel, but it shows “Unknown error”.
After closing the airport detail panel, the timeline in the bottom-left disappears (it does not redraw). Refreshing the page restores it.
In DevTools, the METAR API request from the page hangs pending with no status code (Safari shows Status: —, Source: —, and no response).
Console shows a JS error in Windy code:
TypeError: undefined is not an object (evaluating 'B.prev') from effects.js.
Key evidence (sanitized)
A) JS error report (from Windy error JSON / console)
errorID: typeerror-undefined-is-not-an-object-evaluating-bprev
overlay: rain
runningPhase: 3_redrawFinished
msg: TypeError: undefined is not an object (evaluating 'B.prev')
script: effects.js (line: 1, col: 8435)
Stack trace mentions: _shared/effects.js and _shared/each.js
latestBcast includes: store: poisTemporary metars ...
B) Network request hanging (pending)
Example request (PLEASE NOTE: I’m not posting any token; below is the same endpoint without auth params):
GET https://node.windy.com/airports/metar/ZLLL?pr=0&sc=40
In the logged-in Windy page, the corresponding fetch/XHR request stays pending and shows no status (—) and no response.
C) Important observation: Logging out fixes it
If I log out, the issue disappears: airport detail loads normally and the timeline does not vanish.
This indicates the problem is strongly tied to logged-in flow (auth/token2/uid path) rather than the endpoint being down globally.
Also, directly opening the endpoint in the browser address bar (without auth params) returns content quickly, so node.windy.com is reachable in general. The “pending with no status” only appears when the request is made from the logged-in windy.com page.
Reproduction steps
Open windy.com and log in.
Switch overlay to Rain / Thunderstorm.
Open an airport page / click an airport POI (e.g., ZLLL, also seen with other airports).
The right-side airport details panel shows “Unknown error”.
Close the panel → the timeline disappears (bottom-left).
Check console: TypeError ... B.prev in effects.js.
Check Network: node.windy.com/airports/metar/... request remains pending with no status/response.
Expected result
Airport details should load (METAR/TAF data if available), and closing the panel should not affect the timeline.
No JS TypeError in effects.js.
Actual result
“Unknown error” in airport details.
Timeline disappears after closing the panel.
JS TypeError in effects.js (B.prev undefined).
METAR request hangs pending only in logged-in page flow.
Notes / additional tests
Reproduced across multiple browsers and also another PC, so likely not a single-browser issue.
Clearing site data did not resolve it.
Logging out resolves it consistently.

Thanks!

Error no: 1 Copy

Error no: 2 Copy

Error no: 3 Copy

"errorID": "resizeobserver-loop-completed-with-undelivered-notifications",
"overlay": "wind",
"runningPhase": "3_redrawFinished",
"timestamp": 1769604636124,
"runningMinutes": 0,
"type": "error",
"msg": "ResizeObserver loop completed with undelivered notifications.",
"url": "https://www.windy.com/?36.513,103.623,8",
"ver": "48.1.1",
"target": "index",
"platform": "desktop",
"device": "desktop",
"latestBcast": "store: _cloudSync (808ms ago at 1769604635316)
store: favOverlaysDesktop (808ms ago at 1769604635316)
bcast: rqstOpen menu (123ms ago at 1769604636001)
bcast: pluginOpened menu (34ms ago at 1769604636090)
idb: _nativeSync (21ms ago at 1769604636103)",
"script": "?36.513,103.623,8",
"line": 0,
"col": 0,
"stack": null
}

Error no: 4 Copy

"errorID": "resizeobserver-loop-completed-with-undelivered-notifications",
"overlay": "wind",
"runningPhase": "3_redrawFinished",
"timestamp": 1769604636074,
"runningMinutes": 0,
"type": "error",
"msg": "ResizeObserver loop completed with undelivered notifications.",
"url": "https://www.windy.com/?36.513,103.623,8",
"ver": "48.1.1",
"target": "index",
"platform": "desktop",
"device": "desktop",
"latestBcast": "store: _cloudSync (758ms ago at 1769604635316)
store: favOverlaysDesktop (758ms ago at 1769604635316)
bcast: rqstOpen menu (73ms ago at 1769604636001)",
"script": "?36.513,103.623,8",
"line": 0,
"col": 0,
"stack": null
}

Error no: 5 Copy

"errorID": "resizeobserver-loop-completed-with-undelivered-notifications",
"overlay": "wind",
"runningPhase": "3_redrawFinished",
"timestamp": 1769604636282,
"runningMinutes": 0,
"type": "error",
"msg": "ResizeObserver loop completed with undelivered notifications. (repeated)",
"repeated": 10,
"url": "https://www.windy.com/zh/-菜单/menu?36.513,103.623,8",
"ver": "48.1.1",
"target": "index",
"platform": "desktop",
"device": "desktop",
"latestBcast": "store: _cloudSync (966ms ago at 1769604635316)
store: favOverlaysDesktop (966ms ago at 1769604635316)
bcast: rqstOpen menu (281ms ago at 1769604636001)
bcast: pluginOpened menu (192ms ago at 1769604636090)
idb: _nativeSync (179ms ago at 1769604636103)",
"script": "menu?36.513,103.623,8",
"line": 0,
"col": 0,
"stack": null
}

kerryeva

Update: After logging in, if I turn off the “Display all times in UTC” option, the symptoms seem to disappear.

kerryeva

Even in the latest (newer) web test version, the issue still occurs. I noticed that recent web updates changed the detailed location’s time/weather timeline (it looks different from the app). Could this be related? In the app, the same issue does not happen even when “Display all times in UTC” is enabled.
Note: Safari gets stuck/hangs, while Chrome crashes the page.

Suty

@kerryeva Hello and thank you for reporting. I already forwarded to our devteam.