Send logs to support
Where the Open logs folder button is, which file matches which problem, and what is inside them before you send one.
On this page
Every time a profile's browser starts, LoginDeck writes down what the browser printed on its way up. When a profile won't open, that file says why, and it is the one thing support needs from you.
📂 Open the logs folder#
There are two ways in, and both open the same folder.
- In the left sidebar, click About.
- Under Versions, click Open logs folder.
The hint under the button says it plainly: Every launch records what the browser printed on its way up. This is the folder to look in when a profile will not open.
The other way finds you: when a launch fails, the dialog The profile did not open has Open logs folder as its own button. Use that one — it saves you hunting for the profile.
🗂️ Where the folder is#
If you'd rather go there yourself, paste the path into File Explorer's address bar:
%APPDATA%\LoginDeck\data\logsOn a Mac:
~/Library/Application Support/LoginDeck/data/logs📝 Which file to send#
| File | What it holds | Send it when |
|---|---|---|
launch-<profile id>.log | The last launch of that one profile: the engine it used, the switches it was given, which timezone was chosen and how, then everything the browser printed, then the exit code | A profile won't open, or opens and closes |
launch-<profile id>.prev.log | The launch before that one | The app crashed and you restarted it — this is the launch that explains the crash |
launch-history.log | One line per browser exit, across every profile, with the last few lines of output when the exit wasn't clean | "It was fine last night and broken this morning" |
app.log | LoginDeck's own trouble log: unexpected errors, a window or helper process that died, and the reason | The app itself crashes, won't open, or shows a blank window |
taskbar-<profile id>.log, show-<profile id>.log | The Windows helpers that name a profile's taskbar button and bring its window forward | The Show button does nothing, or a profile's taskbar icon is wrong |
One more sits a folder above the rest, because it is written while the app is closed:
%APPDATA%\LoginDeck\updater.logSend that one if an update won't install, or if LoginDeck won't start after an update. See The app won't install or open.
🔎 Finding the right profile's log#
File names use the profile's id, not its name, so a folder with thirty profiles in it has thirty launch-…log files.
- Easiest: sort the folder by Date modified. The profile you just tried is at the top.
- Or press Open logs folder from the failure dialog itself — you then know the newest file is the one.
🔐 What's in a log before you send it#
Worth knowing, since you're sending it to someone:
- The browser's own output — errors, warnings, crash lines. This is the useful part.
- The switches the browser was started with, which include the window size, language, user-agent and the profile's folder path on your disk.
- Your proxy's address and port, if the proxy has no username. A proxy that needs a login is reached through a loopback address on your own computer instead, so its password never appears in the log.
- The timezone that was chosen, and whether it came from the proxy lookup or from the profile.
There are no cookies, no site passwords and no page contents in these files.
Send the text of the message too
The log explains what the browser did. The dialog text explains what LoginDeck decided. Support needs both — copy the message out of the dialog before you close it.
ℹ️ Good to know#
- Logs are kept per profile, one generation back. Launching a profile again overwrites its current log and pushes the old one to
.prev.log, so grab the file before you retry. - Deleting anything in this folder is safe. Nothing in it is needed to run a profile.
- These logs stay on your computer. Nothing is uploaded, and they are not part of sync.
- The folder is created the first time a profile launches, so a brand-new install may open it empty.
Ready to write in? Contact support lists everything to attach.