Gmail not working and whatsapp not showing the QR code
Hi! When I try to add my Gmail account it shows the following error: Erro 400: invalid_request Missing required parameter: client_id
Whatsapp is ln an infinite QR code lead and it doesn't appear even after quitting and opening the app again.
Can someone give me any tips? Telegram worked fine!
I'm having the same issue also. Using Mac Monterey version 12.3.1 (21E258)
Yes, I also tried all that multiple times and nothing. - I do have Telegram and IG working. Nothing else.
Station developers, can we take a look at this, please? Or does any of you has a tip about a similar app?
Thank you!

I have the same problem. Is this discontinued or something?

I've been having the same issue with Gmail since March 4th (Windows 10 and Windows 11). Disappointing to see that there seems to be no movement towards resolving this. Just checked again 4/26/22 on Windows 10 and the same issue persists.
Does this mean that Station no longer supports Google apps? Is Station shutting down development?
It's been a month and while I don't like that Google is much of the web, without Google support Station is basically unusable for anyone using Google sign-on now.
Since the team hasn't responded for a month can we assume it's something that isn't going to change?
Which app do the rest of you recommend upgrading to as a replacement?
Hi @robwired, I am currently using Rambox as an alternative.
Hi @robwired, I am currently using Rambox as an alternative.
Thank you for the tip. I think we won't get anywhere with Station, such a pity.
Hi @robwired, I am currently using Rambox as an alternative.
Nice one!!
@robwired I've tested out ten similar applications - the top options I've found to be Rambox and Wavebox, but I ended up going with Vivaldi for my solution (use case at the bottom of this post).
Depending on what your use case is, any of the following may or may not work, but they all had significant shortcomings for my needs (integrating g-suite, external webpages, pushing out configuration settings to my student workers).
- Rambox
- Wavebox
- Hamsket - had similar issues with google chat and other g-suite tools
- Franz
- Ferdi - good looking application but the current state of it is in chaos after it seems some personal drama has emerged with its maintainer. I'm looking to check back in and see how it shakes out.
- Ferdium - a fork of Ferdi with some folks trying to resurrect the project. Not currently accessible. Might be interesting to circle back to.
- Sidekick
- WebCatalog - Singlebox (they have a suite of tools that work together) - Was laggy for me and didn't allow for repositioning tiles on the dashboard
- Biscuit (didn't evaluate this one personally)
- SigmaOS (didn't evaluate this as my work machines for this project are all windows)
For my needs, I actually just settled on using the Vivaldi browser. I needed a tiled view of live webpages as a heads up display for my work study students and that ended up free and works great.
@BluekittyMeow Thank you for the very detailed reply and multiple suggestions.
For my needs, I actually just settled on using the Vivaldi browser. I needed a tiled view of live webpages as a heads up display for my work study students and that ended up free and works great.
Do you use the speed dial function of Vivaldi as a replacement for Station? Because I don't really understand how it can work as an all-in-one messenger, which is what I needed to stop having so many open apps on my desktop.
This project is currently not being actively maintained (i.e. the owners aren't going through the issues) but if the community steps in, we may be able to help.
Here is my proposal: @F4Ke and @magne4000, would you be able to answer my questions? It would be really helpful.
- How likely is it that someone (I could try and do it if I learned the skills) could port this to Tauri? It looks like the main language used is Typescript, which is similar to Javascript, but I don't know if it would require any changes in order to port it. Based off of what you know, how hard would it be?
- From what I can tell, I think the problem with Google signin is that the app requires an API key of some sort (the Client ID mentioed). From a quick google search, the solution may just be obtaining a new key and slotting it in in the correct place. My theory is that the maintainers just didn't have time to update the API key, and so it just expired. That is why no one can sign in. @F4Ke and @magne4000, can you confirm this?
- I would be willing to spend my time developing and maintaining this wonderful app, but I would preferably have some help from the original devs. Are you open to this option @F4Ke and @magne4000 (sorry for the repeated mentions, I just want to make sure you see this).
So what do you think? Are there any people in the community that have the knowledge to answer these questions, and/or help if a new project is made in Tauri/I become the maintainer?
@TheRealGramdalf
- How likely is it that someone (I could try and do it if I learned the skills) could port this to Tauri? It looks like the main language used is Typescript, which is similar to Javascript, but I don't know if it would require any changes in order to port it. Based off of what you know, how hard would it be?
Last time I checked (more than a year ago), Tauri was lacking functionalities around Webviews support and security. I do not remember exactly what were the issues though. Here are a few things to note:
- We started implementing Chrome Extensions supports in Station. I assume this will not work in Tauri
- We preload scripts in all Webviews
- We communicate with Webviews (send and receive messages, with handlers created by preload script)
- And more that I forget
In Station, there is a good chunk of code living in a "Worker" process, with it's own framework, that is just a renderer without a Window. This has been done to circumvent an issue with main process blocking the renderers. This Worker handles all the internals of Station, and allows processes to communicate with each others. Currently it's kinda slow because of how Electron works, it would benefit being re-implemented in a child process of the main process (so for Tauri in Rust).
Regarding the Typescript part, Tauri surely has tutorials that explains how to properly dev and build it to JS.
- From what I can tell, I think the problem with Google signin is that the app requires an API key of some sort (the Client ID mentioed). From a quick google search, the solution may just be obtaining a new key and slotting it in in the correct place. My theory is that the maintainers just didn't have time to update the API key, and so it just expired. That is why no one can sign in. @F4Ke and @magne4000, can you confirm this?
Actually, we closed the project on Google's side, so the key is indeed expired. There are 2 solutions:
- Create another API key with a new Google account
- Update gmail definition to remove
bx_multi_instance_configand updatestart_urlso there is no reference touserIdentityin it. It will bypass the first installation screen where you have to choose an account (that's the part that need the Google API key). The only drawback is that, if you have multiple Gmail installed, Station will have more difficulties finding the right Gmail App to go to when you click a Gmail link from another App (but that's currently bugged so not that big of a deal IMO)
- I would be willing to spend my time developing and maintaining this wonderful app, but I would preferably have some help from the original devs. Are you open to this option @F4Ke and @magne4000 (sorry for the repeated mentions, I just want to make sure you see this).
So what do you think? Are there any people in the community that have the knowledge to answer these questions, and/or help if a new project is made in Tauri/I become the maintainer?
You can ping me whenever you have a bunch of questions.
If you eventually become familiar with the code base I could put you as a maintainer if this repo.
Rewriting this for Tauri will require almost a full rewrite of the app though. The only thing I would keep are the manifests definitions, and some business logic found in the Worker. I say that because a good chunk of the code base is heavily Electron related.
If you choose to keep it under Electron, just know that upgrading Electron is horrendous, some versions took us weeks to integrate.
If I haven't discouraged you :sweat_smile:, good luck with this endeavour :mechanical_arm:!
Thanks for the information @magne4000! Unfourtunately, life caught up with me. I'm pretty busy at the moment, but I'll leave this on the backburner. There may not be a need, given that by now ferdium has been released, but if it arises in the future, I may look into this again. The information you have there is really valuable.
Sorry for not replying sooner, it's a combination of life and notifications not being set up.