Archive:HOW-TO:Find and post Kodi.log for iOS: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
(Created page with '{{Notice|Cut and paste draft from a forum post I normally use. Will pretty up and improve soon!}} We need the XBMC.log file to be able to help you Warning: if you password prot…')
 
No edit summary
 
(36 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Notice|Cut and paste draft from a forum post I normally use. Will pretty up and improve soon!}}
{{outdated}}
{{Notice|{{Bigger|See '''[[Log file/Easy]]''' for an easier method of getting the XBMC.log file.}} }}
In most cases when you have an issue we need the '''[[Log_file]]''' file (a.k.a., the debug log) to be able to help you!


We need the XBMC.log file to be able to help you
'''''Warning:''' if you password protect any of your media shares then that password can be exposed in your log file and you won't want that just hanging out on the internet. If this applies to you then you will want to replace any mention of your passwords with asterisks or something so that we still know you had used a password at one point (since that in itself is information that may or may not be important).''


Warning: if you password protect any of your media shares then that password can be exposed in your log file and you won't want that just hanging out on the internet. If this applies to you then you will want to replace any mention of your passwords with asterisks or something so that we still know you had used a password at one point (since that in itself is information that may or may not be important).
# First you want to enable debugging on XBMC. Go to System settings -> System -> Debugging. Make sure "enable debug logging" is on. At this point you should see some weird text pop up on the screen.
 
# Exit and re-enter XBMC or reboot the iOS/ATV2 device so that the debug log contains start-up information as well. Every time you exit/re-enter XBMC a fresh XBMC.log file is made.
First you want to enable debugging on XBMC. Go to System settings -> System -> Debugging. Make sure "enable debug logging" is on. At this point you should see some weird text pop up on the screen.
# Now do whatever it is you normally do to experience the issue in XBMC. Even if it doesn't do anything on screen it will probably still record useful information in the log file that we can use. It will show us what XBMC tried to do and hopefully why it wasn't able to do it.
 
# Grab a copy of Cyberduck or FileZilla, both free and both work on Mac and Windows.
Now do whatever it is you normally do to experience the issue on the ATV2. Even if it doesn't do anything on screen it will probably still record useful information in the log file that we can use. It will show us what XBMC tried to do and hopefully why it wasn't able to do it.
# Use the program to make a SFTP connection. The IP will be whatever IP the ATV2 has
 
# On the ATV2 you can find the IP address by exiting XBMC, and in the normal ATV2 menu go to Settings -> General -> About. Then look for "IP Address" and use the numbers listed there. It will be something like 192.168.1.4, or something similar that has 4 groups of numbers.
Grab a copy of Cyberduck or FileZilla, both free and both work on Mac and Windows.
# The username for the connection will be "root" and the password will be "alpine" by default.
 
# Make the connection and you should see folders and files. Find your way to
Use the program to make a SFTP connection. The IP will be whatever IP the ATV2 has
#: <code>/private/var/mobile/Library/Preferences/</code>
 
# That is the folder that has XBMC.log
You can find the IP address by exiting XBMC, and in the normal ATV2 menu go to Settings -> General -> About. Then look for "IP Address" and use the numbers listed there. It will be something like 192.168.1.4, or something similar that has 4 groups of numbers.
# You should be able to just click and drag the file off to your computer to make a copy. Open it with a text editor, select all, and paste it to a site like http://xbmclogs.com or http://pastebin.com (since it will be a very large file). Then mention the url of the pastebin file you just made in your post reporting the issue.
 
The username for the connection will be "root" and the password will be "alpine" by default.
 
Make the connection and you should see folders and files. Find your way to
 
var/mobile/Library/Preferences/
 
That is the folder that has XBMC.log
 
You should be able to just click and drag the file off to your computer to make a copy. Open it with a text editor, select all, and paste it to a site like pastebin.com (since it will be a very large file). Then mention the url of the pastebin file you just made in your post reporting the issue.
 
[[Category:iOS]]

Latest revision as of 06:11, 12 July 2020

Time.png THIS PAGE IS OUTDATED:

This page or section has not been updated in a long time, no longer applies, refers to features that have been replaced/removed, and/or may not be reliable.

This page is only kept for historical reasons, or in case someone wants to try updating it.

Emblem-important-yellow.png NOTICE:
See Log file/Easy for an easier method of getting the XBMC.log file.

In most cases when you have an issue we need the Log_file file (a.k.a., the debug log) to be able to help you!

Warning: if you password protect any of your media shares then that password can be exposed in your log file and you won't want that just hanging out on the internet. If this applies to you then you will want to replace any mention of your passwords with asterisks or something so that we still know you had used a password at one point (since that in itself is information that may or may not be important).

  1. First you want to enable debugging on XBMC. Go to System settings -> System -> Debugging. Make sure "enable debug logging" is on. At this point you should see some weird text pop up on the screen.
  2. Exit and re-enter XBMC or reboot the iOS/ATV2 device so that the debug log contains start-up information as well. Every time you exit/re-enter XBMC a fresh XBMC.log file is made.
  3. Now do whatever it is you normally do to experience the issue in XBMC. Even if it doesn't do anything on screen it will probably still record useful information in the log file that we can use. It will show us what XBMC tried to do and hopefully why it wasn't able to do it.
  4. Grab a copy of Cyberduck or FileZilla, both free and both work on Mac and Windows.
  5. Use the program to make a SFTP connection. The IP will be whatever IP the ATV2 has
  6. On the ATV2 you can find the IP address by exiting XBMC, and in the normal ATV2 menu go to Settings -> General -> About. Then look for "IP Address" and use the numbers listed there. It will be something like 192.168.1.4, or something similar that has 4 groups of numbers.
  7. The username for the connection will be "root" and the password will be "alpine" by default.
  8. Make the connection and you should see folders and files. Find your way to
    /private/var/mobile/Library/Preferences/
  9. That is the folder that has XBMC.log
  10. You should be able to just click and drag the file off to your computer to make a copy. Open it with a text editor, select all, and paste it to a site like http://xbmclogs.com or http://pastebin.com (since it will be a very large file). Then mention the url of the pastebin file you just made in your post reporting the issue.