ferdium
Launching Slack shows: This browser won’t be supported starting September 1st, 2024. Update your browser to keep using Slack.
Preflight Checklist
- [X] I have read the Contributing Guidelines for this project.
- [X] I agree to follow the Code of Conduct that this project adheres to.
- [X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Problem Description
When launching Slack, it prints this warning before allowing to login:
This browser won’t be supported starting September 1st, 2024. Update your browser to keep using Slack. Learn more
the learn more is: https://slack.com/help/articles/1500001836081 where is says:
| Browser version | End of support |
|---|---|
| Chrome 116 and below | September 1, 2024 |
| Firefox 117 and below | September 1, 2024 |
| Edge 116 and below | September 1, 2024 |
| Safari 16 and below | September 1, 2024 |
Proposed Solution
maybe the internal browser needs updating?
Alternatives Considered
already on host system the firefox/chrome are much newer, the error seem to report on the internal browser used by ferdium..
Additional Information
No response
This is just a problem where the useragent needs updating. See also #1461, where the old useragent causes different loading behavior.
confirm that is correct, after updating the agent on global or slack specific error goes away :) I'm ok w/closing, otherwise maybe some kind of automation could be left at the hand of Ferdium where by it automatically sends the latest version? maybe it already does and it was not set up right on my end..
@stormy1777 the internal browser is chromium updated through electron. Since we are very often upgrading electron, we should be up to date (Ferdium 6.7.4 contained Chromium 124, while version 6.7.5 contains Chromium 126). You can check what version is reported by Ferdium in a service by going to the url https://whatmyuseragent.com/ in the navigation bar. If what slack says does not correspond to what you see on this website, then you should indeed put a custom useragent in this service to fix it. On our end, I am pretty sure we always send the latest version of the chromium supported, but it might not parsed correctly on their end.
As a workaround, you get set the User Agent to:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Slack/4.39.90 Chrome/127.0.6533.72 Electron/13.1.9 Safari/537.36
This is from #1860, but I modified the Chrome bit to be the latest version I have installed.
