Tradovate 'Sign in With Google' Fails on Desktop
You click Sign in with Google in the Tradovate desktop app and hit an error instead of your charts. Here's why Google blocks the embedded login window and how to get back in fast.
You open the Tradovate desktop app, click Sign in with Google, pick your account, and instead of your charts you get an error. Maybe it's a flat “this browser or app may not be secure,” maybe a code like disallowed_useragent, maybe just a login window that closes and dumps you back where you started. The frustrating part is that the exact same Google account logs in fine in Chrome, and it even works on the Tradovate website. So what's actually broken? Nothing on your side. This is Google refusing to run its sign-in flow inside the app's built-in login window, and once you know that, the fix takes about a minute. Below is why it happens, how to get logged in right now from the web platform or with your username and password, and how to make sure it never stalls your automated trading.
Quick Checklist to Get Logged In Now
- Sign in on the web platform. Open the Tradovate web trader in Chrome, Edge, or Safari and use Sign in with Google there. It runs in your real browser, which Google trusts, so it goes through.
- Or use username and password. On the desktop app, ignore the Google button and log in with your Tradovate username and password instead. Direct login works on desktop, web, and mobile.
- No password set? If you only ever used the Google button, click Reset Password, enter your account email, and set a password so you can log in directly from anywhere.
- Don't reinstall in a panic. Reinstalling the desktop app won't fix it, because the block is Google's policy, not a corrupted install.
- Keep automation off this button. If you route TradingView alerts to Tradovate, your orders shouldn't depend on the desktop app's Google login at all.
What's Actually Happening When Google Sign-In Fails on Desktop
When you click Sign in with Google in a desktop app, the app has to show you Google's login page somehow. The Tradovate desktop app does it by opening an embedded browser window, a small web view baked into the app rather than your normal Chrome, Edge, or Safari. That embedded window is where the trouble starts.
Google has spent years tightening its rules on where OAuth sign-in is allowed to run. Embedded browser components let the surrounding app potentially read what you type, inject scripts, or grab session cookies, so Google decided they can't be trusted for account logins. Over a series of enforcement waves, Google moved to block sign-in attempts coming from these embedded web views entirely. Try to log in from one now and Google returns an error rather than a password prompt, commonly worded as “this browser or app may not be secure,” or surfaced as the error code disallowed_useragent. If you click the Learn More link on that error, it explains that the embedded browser Google detected doesn't meet its requirements for signing in.
That's the whole story. The desktop app's login window is an embedded web view, Google won't run its sign-in inside embedded web views, so the Google button in the app hits a wall. Your Tradovate account is untouched, your Google password is fine, and your funding and permissions are unaffected. The proof is that the identical Google account signs in without a hiccup on the Tradovate website, because a real browser is exactly the kind of trusted, full browser Google wants the flow to run in.
This isn't a Windows-only or Mac-only quirk either. The embedded-web-view restriction lives on Google's side and applies to the embedded browser components used on both operating systems, so you can hit the same error in the desktop app whether you're on Windows or macOS. The workaround is identical on both.
Why This Started and Why Reinstalling Won't Help
A lot of traders' first instinct is to uninstall the app, clear everything, and reinstall, assuming the download went bad. Save yourself the time. A fresh install gives you the same embedded login window, which Google will reject in exactly the same way. Clearing cookies, switching your default browser, or updating the app to the newest version doesn't change the outcome either, because none of those touch the actual cause: Google won't authenticate inside an embedded web view, full stop.
It also explains why this can appear to “suddenly” break on a setup that worked before. Google rolled its embedded-web-view block out in stages rather than all at once. An app login flow that slipped through an earlier phase can stop working after a later enforcement wave, with no change on your end. So if the Google button worked in the app months ago and quietly stopped, you didn't do anything wrong, the goalposts moved.
How to Fix It: Sign In From the Web Platform
The cleanest fix is to log in where Google's flow is happy to run: a real browser.
Open a normal browser
Chrome, Edge, Safari, or Firefox all work.
Go to the Tradovate web trader login page
Use the same account you use in the desktop app.
Click Sign in with Google on the web page
Because this is a full browser and not an embedded window, Google shows you the normal account picker and password prompt.
Pick your Google account and approve if prompted
You're in. Same charts, same DOM, same account.
The web trader isn't a stripped-down version of the platform. You get the full charting, order ticket, SuperDOM, ATM strategies, and account tools, and many traders run on the web platform full time. If you're only reaching for the desktop app out of habit, the web login gets you trading immediately with zero setup.
How to Fix It: Use Username and Password on the Desktop App
If you specifically want the desktop app, for its detachable windows or multi-monitor layout, you don't have to use the Google button at all. Tradovate accepts a direct username and password login on the desktop app, and that path has nothing to do with Google's embedded-web-view rule.
Open the desktop app to the login screen
Nothing else to prepare first.
Type your Tradovate username and password
Instead of clicking Sign in with Google, type your credentials into the fields.
Choose the account mode and log in
Pick simulation or live, then log in.
What If You Signed Up With Google and Never Made a Password?
Plenty of traders created their Tradovate account by clicking the Google button on day one and never set a separate password. If that's you, the username-and-password path looks impossible, but it's a two-minute fix:
- On the login screen, click Reset Password (or the equivalent “forgot password” link).
- Enter the username or the email address tied to your Tradovate account, use the same email as your Google account, since that's what's on file.
- Open the reset email Tradovate sends and follow the link to set a password.
- Go back to the desktop app and log in with your username and that new password. You now have a login that doesn't depend on the Google button at all.
If you connect to Tradovate through a prop firm, your login may not use the Google button in the first place. Many firms hand you a dedicated Tradovate username and password when you pass or purchase an evaluation. If yours did, use those credentials directly and skip the Google flow entirely.
Troubleshooting Table
| What you see | What it means | Fix |
|---|---|---|
| Google error in the desktop app (“browser or app may not be secure” / disallowed_useragent) | Google won't run sign-in inside the app's embedded login window | Sign in on the web platform in a real browser, or use username and password on desktop |
| Google login works in Chrome but not in the app | A full browser is trusted; the app's embedded web view is not | Use the web trader, or switch the desktop app to username/password login |
| Reinstalling the app didn't help | The block is Google's policy, not a bad install | Stop reinstalling; use one of the two login paths above |
| You only ever used the Google button and have no password | No direct credentials are set on the account yet | Use Reset Password with your account email, set a password, then log in directly |
| Login worked in the app months ago, now it doesn't | Google tightened embedded-web-view enforcement over time | Move to the web platform or username/password; nothing on your account changed |
| Prop-firm account won't take the Google button | Firm accounts often use dedicated Tradovate credentials | Log in with the username and password your firm issued |
Keep Your Automated Trading Running With PickMyTrade
Here's the bigger point: if your trading depends on you being logged into the desktop app to fire orders, a broken button on one device can freeze your whole day. That's a fragile way to trade. PickMyTrade links your Tradovate account a single time and routes your TradingView alerts to it over its own connection, so your strategy keeps executing no matter which app or login screen is misbehaving on your laptop.
- Link once, trade hands-off. Connect your Tradovate account a single time; there's no desktop login window to babysit before every session.
- Orders fire on their own connection. Your TradingView alerts route straight to Tradovate, so a stuck Google button on the desktop app never blocks a fill.
- Live and demo aware. Point alerts at exactly the account you mean, whether it's a live account or a simulated one.
- Multi-account sync. Mirror the same alert across several Tradovate accounts from one place, without logging each one in separately.
Trade Hands-Off, No Login Window Required
Link your Tradovate account once and let PickMyTrade route your TradingView alerts, so a broken Google button never stalls your strategy.
Start Your Free 5-Day TrialFrequently Asked Questions
The desktop app opens the Google login inside an embedded browser window, and Google no longer allows sign-in from embedded web views for security reasons. Google blocks the request and shows an error instead of completing the login. It's a Google policy, not a broken password, which is why the same Google account signs in fine from a real browser.
Open the web platform in a normal browser like Chrome, Edge, or Safari and use Sign in with Google there, where the flow runs in the real browser Google trusts. Or skip Google entirely and log in with your Tradovate username and password directly in the desktop app, which works on every platform.
Use the Reset Password link on the login screen and enter the email address tied to your Tradovate account. Tradovate emails you a reset link so you can set a password, then you can log in with your username and password anywhere, including the desktop app, without touching the Google button.
Your account is fine. This is a compatibility gap between the desktop app's embedded login window and Google's current security rules, not a problem with your credentials or funding. Signing in from the web or with username and password confirms the account works normally.
Yes. The embedded-web-view restriction is on Google's side and applies to embedded browser components on both Windows and macOS, so the Google button can fail in the desktop app on either operating system. The web platform workaround is the same on both.
No. The web trader runs the same charts, DOM, order types, and account tools as the desktop app. Plenty of active traders run entirely on the web platform. If you prefer the desktop app for its window layout, just switch your account to username and password login so the Google button stops being a blocker.
Automation shouldn't depend on you sitting at the desktop app at all. A service like PickMyTrade links your Tradovate account once and routes your TradingView alerts to your account on its own connection, so a broken Google button on one device never stops your strategy from firing orders.
This guide is for educational and informational purposes only and is not financial, investment, or trading advice. Trading futures and other leveraged products carries a substantial risk of loss and is not suitable for every investor. PickMyTrade is an independent third-party automation platform and is not affiliated with, endorsed by, or sponsored by Tradovate, Inc. or Bookmap. All related names, logos, and trademarks are the property of their respective owners. Platform features and steps change over time, so always confirm the current process in the official platform documentation before acting.