Applies to: Phone & web
Account access problems
Account access problems in MileLedger usually fall into one of three categories: signing in with the wrong Google account, revoked app permissions, or a corrupted local state. This guide covers each cause and the steps to resolve it.
Steps
- 1
Confirm which Google account is signed in
On phone: tap More → Account and note the email address shown. On web: click the profile avatar and check the email. Compare to the address you expect.
- 2
Sign out and sign in with the correct account
On phone: tap More → Account → Sign Out. Then tap Sign In → Continue with Google and select the correct account. On web: click your avatar → Sign Out, then click 'Sign in with Google' and select the correct account.
- 3
Check Google account permissions
Visit myaccount.google.com → Security → Third-party apps with account access. Confirm MileLedger appears and has not been revoked. If it is missing, complete a fresh sign-in from MileLedger to re-grant access.
- 4
Wait for sync to complete
After signing in with the correct account on the phone app, wait a minute or two for sync to complete, then refresh the web app. Data appears after the first successful sync.
Signed in with the wrong Google account
MileLedger data is tied to a specific Google account. If you sign in with a different account — even one from the same family or organization — you will see an empty or different workspace.
To check which account is signed in: tap More → Account on phone, or look at the profile avatar in the top-right corner of the web app. Compare the displayed email to the address you used when you first set up MileLedger.
To switch accounts on phone: tap More → Account → Sign Out, then sign back in with the correct Google account.
MileLedger app permissions revoked
If you previously removed MileLedger from your Google account's authorized applications, sign-in may fail or produce an empty session.
To restore permissions: visit myaccount.google.com → Security → Third-party apps with account access. If MileLedger does not appear, sign in through MileLedger again — the permission will be re-granted as part of the sign-in flow.
Data not visible after signing in
After signing in with the correct account, data from the phone app must sync to Firebase before it appears in the web app. Open MileLedger on your phone, confirm it is signed in, and allow a few minutes for the initial sync to complete. Then refresh the web app.
If data is missing from the phone app itself, see the missing-trip-history or expense-not-saving troubleshooting articles.
Expense logging disabled or not working
Expense logging in MileLedger requires a Google Sign-In account. If you are not signed in, the Expenses tab will prompt you to sign in. On the Free plan, expense logging is limited to 10 expenses — if you have reached this limit, new expenses cannot be saved until you upgrade to Premium or delete existing expenses.
Important notes
- Each Google account has its own MileLedger workspace. Drives and expenses do not transfer between Google accounts.
- If you delete your Google account, your synced MileLedger data will no longer be accessible. Export your data to CSV before making changes to your Google account.
Common problems
I signed in but the web app shows someone else's data.
You are likely signed in to the web app with a different Google account than you expected. Sign out of the web app and sign back in with your personal Google account — not a shared or family account.
I get an 'access denied' or 'unauthorized' error.
This can occur if MileLedger's Google permissions were revoked. Visit myaccount.google.com → Security → Third-party apps and check whether MileLedger appears. Sign in again from MileLedger to restore access. If the problem persists, contact support at /contact.
Related articles
- Unable to sign in to MileLedger · Troubleshooting
- Password or authentication problems · Troubleshooting
- Session expiration — signed out unexpectedly · Troubleshooting
- Sign in to MileLedger · Getting started
- Changes are not appearing on another device or the web · Troubleshooting
Still stuck? Contact support or browse Troubleshooting.