[Desktop] clicking a downloaded file or on the "Open" button in the "..." menu makes the app unresponsive for a second or so

[sunleos]

Bug Report

Description

Steps to reproduce

1. download a file via the Status browser
2. click on the downloaded file to open it or click on the "Open" button in the "..." menu

Expected behavior

clicking a downloaded file or on the "Open" button in the "..." menu should open the downloaded file

Actual behavior

clicking a downloaded file or on the "Open" button in the "..." menu makes the app unresponsive for a second or so

Additional Information

• Status app version: release v2.38 https://ci.infra.status.im/blue/organizations/jenkins/status-app%2Frelease/detail/release%2F2.38.x/89/artifacts
• Operating System and version: Windows 11
• Mobile Device: n/a

[sunleos]

@micieslak & @caybro, it could be something related to broken links.

[caybro]

@micieslak & @caybro, it could be something related to broken links.

I don't think so... if the file eventually opens, it's just being slow (it's Windows :)

[caybro]

And btw, you are clicking a huge binary file, so how do you expect the file to be "shown"? It's just being executed/opened

[sunleos]

And btw, you are clicking a huge binary file, so how do you expect the file to be "shown"? It's just being executed/opened

just retested

when I click on a downloaded .exe file or click on the "Open" button in the "..." menu, I expect that it launches or if it is a document (e.g. a pdf file), then it is opened with the default app, but I'm not sure if it is a bug (i.e. it worked before) or just a missing feature.

currently, clicking on a downloaded .exe file or clicking on the "Open" button in the "..." menu just freezes the app for 1-2 seconds and then app is back to normal but nothing else happens with the file.

[caybro]

And btw, you are clicking a huge binary file, so how do you expect the file to be "shown"? It's just being executed/opened

just retested

when I click on a downloaded .exe file or click on the "Open" button in the "..." menu, I expect that it launches or if it is a document (e.g. a pdf file), then it is opened with the default app, but I'm not sure if it is a bug (i.e. it worked before) or just a missing feature.

currently, clicking on a downloaded .exe file or clicking on the "Open" button in the "..." menu just freezes the app for 1-2 seconds and then app is back to normal but nothing else happens with the file.

OK, might be (yet another) problem with a Windows filepath. Can you try:

• on macOS or Linux?
• and second, what happens if you click the other menu item (Show in Folder); does it open something?

[caybro]

"Show in folder" works under Linux:

[caybro]

Clicking the (finished download) extracts the tgz and opens the file explorer in the target directory 🤌

[sunleos]

And btw, you are clicking a huge binary file, so how do you expect the file to be "shown"? It's just being executed/opened

just retested
when I click on a downloaded .exe file or click on the "Open" button in the "..." menu, I expect that it launches or if it is a document (e.g. a pdf file), then it is opened with the default app, but I'm not sure if it is a bug (i.e. it worked before) or just a missing feature.
currently, clicking on a downloaded .exe file or clicking on the "Open" button in the "..." menu just freezes the app for 1-2 seconds and then app is back to normal but nothing else happens with the file.

OK, might be (yet another) problem with a Windows filepath. Can you try:

• on macOS or Linux?
• and second, what happens if you click the other menu item (Show in Folder); does it open something?

Ah, I just have two Windows machines, hence, can't check it on MacOS or Linux.

clicking on the "Show in folder" open the right folder with the downloaded file, hence, it works on Windows 11. A slight UX issue that the downloaded file is not selected to highlight it in the folder, but that could be a separate ticket.

[caybro]

And btw, you are clicking a huge binary file, so how do you expect the file to be "shown"? It's just being executed/opened

just retested
when I click on a downloaded .exe file or click on the "Open" button in the "..." menu, I expect that it launches or if it is a document (e.g. a pdf file), then it is opened with the default app, but I'm not sure if it is a bug (i.e. it worked before) or just a missing feature.
currently, clicking on a downloaded .exe file or clicking on the "Open" button in the "..." menu just freezes the app for 1-2 seconds and then app is back to normal but nothing else happens with the file.

OK, might be (yet another) problem with a Windows filepath. Can you try:

• on macOS or Linux?
• and second, what happens if you click the other menu item (Show in Folder); does it open something?

Ah, I just have two Windows machines, hence, can't check it on MacOS or Linux.

clicking on the "Show in folder" open the right folder with the downloaded file, hence, it works on Windows 11. A slight UX issue that the downloaded file is not selected to highlight it in the folder, but that could be a separate ticket.

OK... so it's likely not a problem with the Windows path; are you sure the former (opening the finished download) isn't being blocked somewhere in the background, e.g. by the antivirus or something? All in all it sounds like it should work, there was an earlier PR from @friofry (#19282) that was fixing this same exact issue (opening files/dirs on Windows) and it's been untouched since then

[sunleos]

@caybro,

That's a good point.

If I download an app .exe build, I always have to go through these screens

Just tested:
Actually, once I complete this step above (i.e. hit Run anyway on that screen) on a build (I do it by just going into my default downloads folder and clicking on a build to trigger these screens above), then I can open that build in our in-app browser as well. But before going through these blue screens, I can not open builds downloaded in our in-app browser.

[sunleos]

@caybro

It looks that clicking on a newly downloaded build, like a build from a PR, in the in-app browser has problems with invoking that Microsoft Defender Smart Screen (see the above), but this works on Chrome.

[caybro]

@caybro

It looks that clicking on a newly downloaded build, like a build from a PR, in the in-app browser has problems with invoking that Microsoft Defender Smart Screen (see the above), but this works on Chrome.

OK then that's likely a packaging or (windows) installer specific issue, probably because using a PR build. Can you reproduce the same using a signed release build?