Report Issue cannot sent - Android App

thimu

The yellow button is disabled.

Expected: Button is enabled

Android Version: 16 API , SDK 36 , One UI Version: 8.0
Device: samsung/r9qxeea/r9q : 16 (Samsung Galaxy S21 FE 5G), Model SM-G990B, Locale: de-DE

MarkNagy

@thimu Hi. Thank you for the report, I will take a look.

thimu

@MarkNagy Hi, The issue still exists in
Android app
version: 50.0.2 (723ed6d)
built: 2026-05-12T08:03:45.6087

MarkNagy

@thimu I am sorry to hear that. I will get back to this issue in a few days. Thanks for the report.

thimu

@MarkNagy
I just sent an error report with success. The issue here with sending the issue report is resolved using version 50.1.1
Thanks!

The error report which I just sent covers a new, other error.

javinpress

I tried sending a bug report via the website earlier today, same issue, the button stays unlit and doesn't allow the report to be sent.

thimu

I sent the error report with success via the Android app. It seems the behaviour is different between app and website.

FYI: Just as a precaution: The content of the ERROR CONSOLE of the new error in the sent error report should be as follows:

{
"errorID": "uncaught-typeerror-r-is-not-a-function",
"overlay": "radar",
"runningPhase": "3_redrawFinished",
"timestamp": 1784045099949,
"runningMinutes": 0,
"type": "error",
"msg": "Uncaught TypeError: r(...) is not a function",
"url": "https://app-webview.windy.com/#?radar,49.615,8.643,9,p:cities",
"ver": "50.1.1",
"target": "mobile",
"platform": "android",
"device": "mobile",
"latestBcast": "bcast: rqstOpen sounding (2ms ago at 1784045099947)
picker: pickerClosed (1ms ago at 1784045099948)
bcast: pluginClosed picker-mobile (1ms ago at 1784045099948)",
"network": {
"downlink": 9.5,
"downlinkMax": null,
"effectiveType": "4g",
"rtt": 0,
"saveData": false,
"type": "wifi"
},
"script": "_shared-client.js",
"line": 20,
"col": 24497,
"stack": "TypeError: r(...) is not a function
at U (https://app-webview.windy.com/v/50.1.1.mob.4aea/plugins/_shared-location-buttons.js:1:3450)
at HTMLDivElement.onclick (https://app-webview.windy.com/v/50.1.1.mob.4aea/plugins/_shared-location-buttons.js:1:3148)
at HTMLDivElement. (https://app-webview.windy.com/v/50.1.1.mob.4aea/plugins/_shared-location-buttons.js:1:5012)
at HTMLDivElement.Qi (https://app-webview.windy.com/v/50.1.1.mob.4aea/plugins/_shared-client.js:20:24366)"
}

⚙️

@MarkNagy, @all Windy staff
Did you receive the error report which I sent?
The sent error report should contain the error console content automatically as shown above, my short step description and an attached mp4 screen recording video file of appr. 14 MB size

Suty

@thimu Could you please send all the details at support@windy.com, we prioritize this communication and it would be more effective to receive the report there.

thimu

@Suty said in Report Issue cannot sent - Android App:

@thimu Could you please send all the details at support@windy.com, we prioritize this communication and it would be more effective to receive the report there.

Just sent to support@windy.com with the subject line:
Bug: Error message when tapping on "Sounding for this point"

@Suty , @MarkNagy

From my point of view, the status of the entire topic is as follows:

The original topic "Report Issue cannot sent - Android App" remains unresolved, as the submission via the app apparently did not go through or was not fully received.
The problem also exists on the Windy website - independent of the original post, as @javinpress noted; see:
https://community.windy.com/post/229760
This therefore constitutes a separate, additional issue.

In addition to fixing the problem, I suggest the following further improvements:

When submitting an error report via the app or website, the system should automatically include:

error messages from the error console (if any exist),
the Windy version number, and
relevant details regarding the device or operating system used (if necessary). As a user reporting an error, I want the process to require as little effort as possible.

The app or website should display not only a submission confirmation but also a receipt confirmation. Users take the trouble to report an error, and it should not happen that the report goes unnoticed while failing to actually reach Windy.