Support
Write to the developer.
G-garry is made by one person. Questions, bug reports and feature requests all go to the same address, and are read.
| samkharadzemerab@gmail.com | |
| Cost | Free. There is no paid tier and no account. |
| Reply | Reports that come with steps to reproduce get answered first. |
So the problem can be reproduced
- your Chrome version (
chrome://version) and your operating system; - the G-garry version, from
chrome://extensions; - what you did, what you expected, and what happened instead;
- whether the page you were debugging is public, and if so its URL;
- any errors from the DevTools console, or from the extension's own service worker page
on
chrome://extensions→ Inspect views.
Before you attach a session file
A HAR or session export describes real traffic from a real page. G-garry redacts credential-bearing headers by default, but bodies and URLs can still carry personal data, internal hostnames or tokens. Open the file and check it before sending it to anyone, including me.
The panel is empty
Open the G-garry panel in DevTools, then reload the page, so the calls happen with the
panel watching. Note also what the panel covers: fetch() and
XMLHttpRequest. Other transports, such as navigator.sendBeacon
and WebSocket, do not appear in the log.
The log disappeared
That is deliberate. The request log lives in session storage and is cleared when the browser closes. Export a session file if you need to keep one.
Where the recorded data goes
Nowhere. There is no server, no telemetry and no crash reporting, so nothing reaches me unless you send it yourself. The privacy policy sets out exactly what the extension reads and where it keeps it.