Kodi / diagnostic logging · Publisher-documented guidance; UK IPTV account compatibility not tested. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Begin with a reproducible action
A useful log accompanies a clear statement of what should happen and what actually happens. Pick one small action that reproduces the problem, such as opening an authorised sample or selecting the failing menu. Avoid combining several unrelated faults in one session. Note the application version and device so the log has a practical context rather than arriving as an unexplained large text file.
Follow the application’s logging workflow
Kodi’s official easy-log guide describes enabling debug logging, restarting through its power menu and reproducing the fault while logging is active. The order matters because the startup and failing action provide different evidence. Consult the applicable guide rather than disconnecting power as a substitute for an orderly restart. This article describes preparation; it does not upload a log or authorise somebody else to inspect an account.
Inspect what would be shared
Logs can contain paths, addresses and other details about a setup. Review the actual content before selecting a support channel, and keep credentials, complete private source addresses and unrelated personal material out of public posts. Do not assume that every uploader or application automatically removes everything sensitive. If a support team needs a particular component log, clarify that narrow request instead of collecting every available detail indiscriminately.
Send context with the relevant record
When sharing is appropriate, include the symptom, reproduction steps and time of the observed failure through the chosen legitimate route. A screenshot of the final error may help describe the symptom but does not replace a log that actually captured the failing operation. Turn diagnostic collection back to the intended ordinary state after the investigation. The goal is useful evidence, not an indefinitely growing collection of private technical history.
Questions, answered
Should I upload any log before reading it?
Inspect the actual content and choose an appropriate support route first. A logging guide explains capture, but it does not establish that every generated file is suitable for a public post or that every private value has been removed.