This should hopefully stop the stream of unhelpful reports.
There is now a dialog yes/no to confirm creating the issue/uploading log. Plently of issues have undoubtedly come from curious users checking any setting they can.
Some issues have also been failing to submit due to the unicode error that caused the issue also causing the issue reporter to fail. It seems to always be from unicode contained in large JSON or XML files which is included in the exception args. When the issue formatter tries to split the exception data on newlines there is then a list hundreds of items long that is passed to the xbmcgui Dialog object which only takes a max of 3, causing failure. We now omit the data which caused the exception which is ok because ther is enough information in the log to get to the source which caused it including the position of the offending unicode character.
This should hopefully stop the stream of unhelpful reports.
There is now a dialog yes/no to confirm creating the issue/uploading log. Plently of issues have undoubtedly come from curious users checking any setting they can.
Some issues have also been failing to submit due to the unicode error that caused the issue also causing the issue reporter to fail. It seems to always be from unicode contained in large JSON or XML files which is included in the exception args. When the issue formatter tries to split the exception data on newlines there is then a list hundreds of items long that is passed to the xbmcgui Dialog object which only takes a max of 3, causing failure. We now omit the data which caused the exception which is ok because ther is enough information in the log to get to the source which caused it including the position of the offending unicode character.