Request Log
The Request Log shows what Grafida has been saying to your site, and what your site said back. It is a troubleshooting tool: when something does not work and the message on screen is not enough to explain why, this is what tells you — or whoever is helping you — what actually went over the wire.
It is off by default. Turn on Debug mode in Settings, and a Request Log row appears in the sidebar, just above Help.
What is recorded
The last 20 requests, newest first. Each entry shows the method and address, the response status, how long it took, and the time it happened. Tap an entry to open it, and you get the request's headers and body followed by the response's.
JSON is tidied up so you can read it. A body that is not text — a picture on its way up to your site, say — is named as such rather than spilled across the screen as gibberish, and a very large one is cut short with a note saying so.
Every request Grafida makes to your site is recorded: publishing an article, listing categories, uploading a picture, fetching a site's icon or its editor stylesheet.
What is not recorded
Nothing is written to your device's storage. The log lives in memory for as long as Grafida is running, and it is emptied when Grafida starts, when you switch to another site, and when you turn Debug mode off. That is deliberate: it is a live window on what is happening now, not a history to look back through.
Switching sites clears it because the log has no notion of which site an entry came from. Rather than leave you comparing one site's requests against another's without a way to tell them apart, Grafida starts again.
Your API token is hidden
Your Joomla! API token is masked everywhere it could appear — in the Authorization and
X-Joomla-Token headers, and anywhere it turns up inside an address or a body — leaving only its
first four and last four characters.
That masking happens once, on the way in, before an entry is ever stored. What you see on screen is exactly what an export contains; there is no second, more revealing route out.
Tip
The four characters left at each end are enough to tell you which token was used, which is often the answer by itself: if the first four are not what you expect, Grafida is talking to your site with a token you thought you had replaced.
The buttons
Export writes the whole log to a JSON file and opens the device's share sheet, so you can save it
to Files, mail it, or AirDrop it to a Mac. The file is named
grafida-request-log- followed by the date and time.
Clear empties the log. Grafida asks first. It does not turn recording off — use it to wipe the slate immediately before reproducing a problem, so what is left afterwards is only the part that matters.
There is no Refresh button, and none is needed: the list updates itself as requests happen. You can leave it open on one side of the screen in Split View and watch entries arrive as you work.
Important
An exported log has your token masked, but it still describes your site in detail — addresses, article text, category and user numbers. Read it before you attach it to a public bug report or send it to somebody you do not know.
When this will not help
The Request Log shows you what a working, configured site is doing. If Grafida cannot reach your site at all, there may be nothing here worth looking at — a request that never got an answer is recorded, but all it can tell you is that it failed. Start with Connection Troubleshooting instead.