Tradovate iOS App Shows 'No Account' After Face ID
Face ID unlocks the Tradovate iOS app in an instant, but the account screen comes back blank. Here's why that happens and the thirty-second fix that brings your account back.
You open Tradovate on your iPhone, Face ID scans your face, the app unlocks in a fraction of a second, and where your account should be, it just says No Account. No balance, no open positions, no order ticket. The one screen you actually need is blank. That's a gut-punch when the market's moving and you were counting on a quick tap-and-go login. Here's the reassuring part: your account is fine, nothing has been closed or wiped, and the fix takes about thirty seconds. Let's walk through what's happening and how to get your account back on screen fast.
Quick Checklist for the 'No Account' Screen
- Log out fully, then log back in with your username and password, not Face ID. This is the fix nine times out of ten.
- Skip Face ID for one login and type your credentials so the app builds a fresh, complete session that actually loads your accounts.
- Force-close and reopen the app first to rule out a screen that's simply stuck.
- Check Face ID for the app in iOS Settings if biometric login keeps landing you on a blank account.
- Update or reinstall the app if the blank-account screen sticks around even after a manual login.
- Use the web or desktop platform to manage open positions while you sort the phone out.
What "No Account After Face ID" Actually Means
When you sign in to Tradovate on mobile, two things have to happen: the app has to authenticate you, and then it has to fetch the list of trading accounts tied to your login and drop you into one of them. Face ID handles the first part beautifully, it unlocks the app using a session it saved the last time you were signed in. The problem is the second part. If that saved session is incomplete or stale, the app treats you as logged in but never re-runs the step that pulls your accounts, so the account field comes back empty and you see No Account.
This is worth separating from the other login errors you might have hit before. It isn't a wrong password, because Face ID let you in. It isn't a two-factor or device-approval prompt, because there's no prompt at all. And it isn't an entitlement or subscription block, those throw a specific message rather than a silent blank. What you're looking at is a session-state hiccup: the biometric shortcut resumed a session that didn't carry your account list with it.
That's exactly why the manual re-login works so reliably. A full logout throws the half-loaded session away, and signing back in with your username and password runs the whole sequence from scratch, account fetch included. It shows up more often right after an app update changes how sessions are cached, a hint that the build, not your phone, is usually the trigger.
Top Causes of the Tradovate 'No Account' Screen
1. Face ID resumed a partial session
This is the headline cause. Face ID is designed to skip you past the full login flow by reusing a stored session. When that stored session is missing the account data, because it expired, was interrupted, or was written incompletely, you get authenticated but land on an empty account screen. The app isn't broken; it just resumed the wrong snapshot.
2. A recent app update changed how sessions are cached
Blank-account-after-biometric problems cluster around app updates. When a new build tweaks the way login sessions are stored and restored, the older cached session on your device can stop lining up with what the new build expects. The app opens, Face ID passes, and the mismatch leaves your account list empty until you sign in fresh.
3. A stale or expired token behind the biometric unlock
Sessions don't last forever. If your saved session has aged out but Face ID still unlocks the app shell, you end up in limbo, logged in enough to open the app, not logged in enough to load an account. A clean credential login mints a new token and clears it.
4. Face ID is misconfigured for the app
Sometimes the biometric layer itself is the weak link. If Face ID is disabled for the app in your iPhone settings, was recently reset, or is failing intermittently, the login can finish in an odd half-state. Worth a look when the blank account keeps coming back on Face ID logins but never on manual ones.
5. An account-level state that also shows up elsewhere
Occasionally the blank screen isn't about Face ID at all, the account genuinely isn't loading yet. A brand-new prop-firm evaluation that hasn't finished provisioning, or an account the firm hasn't enabled, can read as “No Account” on the app too. Provisioning windows and account rules vary by firm and account size, so if a clean login still shows nothing, check your firm's current process before blaming the app.
How to Fix the 'No Account' Screen: Step-by-Step
Fix a partial session (log out and back in manually)
This is the one that clears it almost every time, so start here. Open the app's menu or account/settings area and choose Log Out (confirm the exact label in your build; fully signing out is the important part, don't just force-close). On the login screen, skip Face ID for this one login and type your Tradovate username and password by hand. Sign in. The app now runs the full login sequence, re-fetches your account list, and drops you into your account instead of a blank screen.
Fix a stuck screen (force-close first, if you haven't)
From the home screen, swipe up from the bottom (or double-press Home on older devices) to open the App Switcher. Find the Tradovate card and swipe it up and off the screen to fully quit the app. Reopen it. If the blank account was just a frozen screen rather than a bad session, it may load correctly now. If Face ID still lands you on “No Account,” move on to the manual login above.
Fix biometric configuration (check Face ID in iOS Settings)
Open Settings › Face ID & Passcode and confirm Face ID is turned on for the Tradovate app under Other Apps. If it keeps misbehaving, toggle Face ID off for the app, log in manually once, then toggle it back on so it re-registers cleanly. Still flaky? Tap Reset Face ID and set it up again, restart the iPhone, and make sure iOS is up to date.
Fix a stale build (update or reinstall the app)
Open the App Store, search Tradovate, and install any pending update. If a blank account survives a manual login, press and hold the app icon, delete the app to wipe its stored session data, then reinstall it from the App Store and log back in with your username and password.
Fix it when the account still won't show (use web/desktop, then check the source)
If a clean reinstall and a manual login still show “No Account,” stop troubleshooting the phone, the account isn't loading from higher up. Log in to the Tradovate web platform in a browser or the desktop app to confirm the account is active and visible there. If it's a prop-firm evaluation that's blank everywhere, contact your firm, the account may still be provisioning or need enabling on their end.
If iOS autofill won't populate your saved credentials, type them in or copy-paste from your password manager. The goal is simply a fresh username-and-password login that rebuilds the session, however you get the characters into the fields is fine.
Troubleshooting Table
| Symptom | What it means | Fix |
|---|---|---|
| Face ID unlocks the app but the account is blank | Biometric login resumed a partial session | Log out fully, sign back in with username and password |
| Manual logins work, Face ID logins go blank | Biometric config or a stale saved session | Toggle/reset Face ID for the app in iOS Settings |
| Blank account started right after an app update | New build changed how sessions are cached | Install the next update, then delete and reinstall |
| Blank even after a clean username-and-password login | Account isn't loading from the server side | Confirm on web/desktop; check with your prop firm |
| Screen frozen rather than genuinely empty | Stuck UI, not a session problem | Force-close from the App Switcher and reopen |
| Face ID itself is failing across other apps | Device-level biometric issue | Reset Face ID, restart, and update iOS |
Prevent This with PickMyTrade
A blank account screen at the wrong moment shouldn't be the thing standing between your strategy and the market. PickMyTrade connects your TradingView alerts straight to your Tradovate account on the server side, so your orders keep firing whether or not your phone cooperates:
- Server-side execution, your automation runs on PickMyTrade's infrastructure, not your handset, so a biometric login glitch never stalls a trade.
- Multi-account sync, mirror the same orders across every connected account without touching the mobile app's account picker.
- Reliable alert-to-order routing, TradingView signals reach Tradovate through a stable bridge instead of a fragile mobile session.
- Hands-off risk management, attach stops and targets automatically so open positions stay protected while you rebuild the app login.
Don't Let a Blank Screen Stop Your Strategy
Automate Tradovate with PickMyTrade so your orders keep firing whether or not your phone cooperates.
Start Your Free 5-Day TrialFrequently Asked Questions
Face ID unlocked the app using a saved session, but that session didn't pull down your account list, so the account field comes back empty. The login itself succeeded, the app just skipped the step that fetches your accounts. Logging out fully and signing back in with your username and password builds a fresh, complete session and your account reappears.
No. Your account, balance, positions, and orders all live on Tradovate's servers, not inside the phone app. A blank "No Account" screen is a display and session problem on the device, not a sign that anything was closed, liquidated, or deleted. A manual re-login brings it all back.
Log out of the app completely, then log back in by typing your username and password instead of using Face ID. That forces the app to build a new session and re-request your account list. It takes about thirty seconds and clears the problem the vast majority of the time.
Face ID resumes a stored session as-is. If that stored session is partial or stale, the app authenticates you but never reloads your accounts, so you land on a blank screen. A full logout throws away that half-loaded session, and a fresh username-and-password login runs the complete sequence, including the account fetch, from scratch.
You don't have to turn it off permanently. Skipping Face ID for a single login and typing your credentials is usually enough to rebuild a clean session. If Face ID keeps dropping you onto a blank account after that, disable it for the app for now, log in manually, and re-enable it once a build fixes the behavior.
If a clean username-and-password login still shows nothing, the issue is above the app. Log in to the Tradovate web or desktop platform to confirm the account is active there. If you trade a prop-firm evaluation, a blank account can also mean the firm hasn't finished provisioning or enabling that account, provisioning windows and rules vary by firm, so check your firm's current process before assuming it's an app bug.
Open the Tradovate web platform in a mobile or desktop browser, or use the desktop app, and log in there. You get full control of your positions and orders while you rebuild the session on your phone, so you're never locked out of a live trade because of a blank screen.
Don't let the mobile app be the only thing routing your trades. When your strategy runs through server-side automation like PickMyTrade, your entries, stops, and exits keep executing on Tradovate even when the iOS app hands you a blank account screen.
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.