Known limitations
Read these before you buy Tree Grower. They are specific to browsers and operating systems; what the format itself does not promise is on the Trust page.
| What | Where | What to expect |
|---|---|---|
| Safari | macOS | Not supported for capture or replay. Use another browser on the list Tree shows you. |
| Vivaldi | Linux | Connects, but pages do not capture. Details. |
| Chrome installed as a Flatpak | Linux, 2.0.8 and earlier | Not found automatically. Fixed in 2.0.11; a workaround for older versions is below. |
| Firefox installed as a Flatpak | Linux | Not supported. Install Firefox from your distribution or from Mozilla's packages instead. |
| “Select where your browser is…” | Linux, 2.0.8 and earlier | A browser chosen by hand does not connect. Fixed in 2.0.11. Details. |
| WebSocket and WebRTC traffic | Everywhere | Not captured and not replayed. Pages that rely on them can replay incompletely. |
Checked on Ubuntu 24.04 with Tree Grower and Tree Player 2.0.8, and with the fixes in 2.0.11.
“Exec format error”
Connection Failed Failed to launch com.google.Chrome: Exec format error (os error 8)
Why. Chrome is installed as a Flatpak. Version 2.0.8 and earlier do not find Flatpak browsers, and the file chosen under “Select where your browser is…” was Chrome's launcher shortcut. That shortcut is a text file, not a program, so it cannot be started directly.
Fix. Update to 2.0.11 or later from Downloads. Flatpak browsers then appear in the list as, for example, “Google Chrome (Flatpak)”, and a launcher you already chose by hand starts working without any action.
On 2.0.8 and earlier. Quit Tree Grower, paste these lines into a terminal, then start Tree Grower again. It opens Chrome and connects by itself.
W=/var/lib/flatpak/exports/bin/com.google.Chrome
[ -x "$W" ] || W="$HOME/.local/share/flatpak/exports/bin/com.google.Chrome"
mkdir -p ~/.config/DOSAYGO/trees
printf '{"selected_browser":{"kind":"Chrome","name":"Google Chrome","path":"%s"}}\n' "$W" > ~/.config/DOSAYGO/trees/config.json
flatpak override --user --filesystem=~/.config/DOSAYGO/trees/profiles com.google.Chrome
The first four lines point Tree at Flatpak Chrome. The last line lets Chrome keep Tree's browser profile between sessions; without it Tree still captures, but sites you sign in to are signed out each time the browser closes. Your license and your collections are not touched.
Install Chrome from Google's own .deb or .rpm package. In Tree Grower choose Browser, then Change…, and pick “Google Chrome”.
“Permission denied”
Failed to launch com.google.Chrome: Permission denied (os error 13)
Why. The file chosen by hand was the launcher shortcut that Google's .deb or .rpm package installs. Like the Flatpak one, it is not a program.
Fix. Update to 2.0.11 or later, where choosing the launcher shortcut works. On older versions, choose Browser, then Change…, and pick “Google Chrome” from the list; a Chrome installed from Google's package is found automatically.
“404 Not Found” after the browser opens
Connection Failed BiDi connection failed: … POST /session failed: HTTP error: HTTP/1.1 404 Not Found
Why. In 2.0.8 and earlier on Linux, a browser chosen with “Select where your browser is…” starts, but Tree then talks to it the wrong way and the connection is refused. This happens even when the file you chose is the right one.
Fix. Update to 2.0.11 or later. A browser you choose by hand is then recognised as Chrome, Chromium, Edge, Brave, Opera, Vivaldi, or Firefox, and any other file is refused with a message saying so. On older versions, choose Browser, then Change…, and pick a browser from the list instead; if your browser is Chrome from Flatpak and is not listed, use the workaround above.
Vivaldi connects but does not capture
Error: Navigate failed: … Chrome target setup timed out; target remains paused
Why. On Linux, Tree connects to Vivaldi but cannot prepare its tabs for capture. We saw this with Vivaldi 8.2, installed both from Vivaldi's package and as a Flatpak. We have not found a setting that avoids it.
Fix. Choose Browser, then Change…, and capture with another browser on the list, such as Chrome.
A small square on a button
In 2.0.8 and earlier, some buttons show a small empty square where an arrow should be, for example on “Continue”, “Create Branch”, and “Back”. This is cosmetic: the buttons work normally. Fixed in 2.0.11.
Settings and logs
Tree keeps its settings, logs, and browser profiles in one folder. On Linux the capital letters matter.
| Path | What it holds |
|---|---|
~/.config/DOSAYGO/trees/config.json | The browser you chose and the collection you last had open. Delete this file and Tree asks you to choose a browser again. |
~/.config/DOSAYGO/trees/logs/ | tree-grower.log and tree-player.log: warnings and errors. |
~/.config/DOSAYGO/trees/profiles/ | The browser profiles Tree uses. They are separate from your everyday browser profile. |
On Windows the folder is %USERPROFILE%\.config\DOSAYGO\trees.
Report a problem
If your message is not on this page, email support@dosaygo.com with:
- A screenshot or the exact text of the error.
- Your operating system and, on Linux, the distribution.
- The Tree Grower or Tree Player version.
- Which browser you use and how it was installed. On Linux, the output of
flatpak listhelps.
Remove tokens and private browsing data from logs before you send them, and do not attach a private collection. See archive handling.