Troubleshoot mobile and browser issues

Atlas works best when the browser can run modern web app features, keep local session state, and display dense research surfaces. Mobile can handle many review tasks, but large PDFs, maps, and multi-panel work are usually better on desktop.

Start with the environment

Record the browser, device, and exact action that failed. Then try a simple reload. If the issue continues, test the same action in another supported browser profile before changing account or project data.

Login problems

If sign-in loops, fails silently, or returns to the wrong state:

1. Confirm the device clock is correct.
2. Disable privacy or script-blocking extensions for Atlas.
3. Allow cookies and site storage for Atlas.
4. Try a private window or a clean browser profile.
5. Clear Atlas site data only after the simpler checks fail.

Upload problems

Large PDFs and multi-file uploads are more reliable on desktop. If an upload fails on mobile, retry from a desktop browser before assuming the source itself is broken.

Also check Troubleshoot source processing if the upload completes but the source never becomes usable.

Layout problems

Dense research surfaces need space. If the workspace feels cramped:

• Use desktop for source review plus notes plus chat.
• Use mobile for reading, checking summaries, and asking focused questions.
• Collapse panels you are not actively using.
• Avoid map editing on very small screens when precision matters.

Browser extensions

Extensions that rewrite pages, block scripts, block storage, intercept downloads, or manage privacy can break web app behavior. Disable them temporarily for Atlas when debugging.

What to send support

Include device type, browser name and version, account email, project name, and the action that failed. If the issue only happens on mobile or only in one browser, say that explicitly.

Common fixes

Related

• Mobile app
• Workspace layout