Hi, I’m having a problem with the debugger in the ShotGrid Desktop app. When there’s an error in my configuration, the debugger only returns generic messages like:
[ERROR] [PROXY] 'str' object has no attribute '_is_remote'
and doesn’t provide detailed information.
In previous versions, the debugger used to show much more information, including detailed tracebacks. Is there a way to restore the old behavior or get more detailed logs for debugging?
I suppose you know about the debug logging switch - How do I turn on debug logging? - SG Developer
Yes, I know, and unfortunately, it’s not that 
In the previous version, errors in the log looked like typical errors in Python IDLE. I mean, you got all the information back then: which file raised the error, in which line, etc. Now, I only get errors like the one I mentioned before. It’s very frustrating when I need to do a quick fix.
It would be interesting to see whether there were changes to hide the tracebacks… it would be unfortunate indeed.
Ok I reinstalled Shotgrid Desktop for newest version, and update config python path, and it starts to work correctly 
I’am interested if problem was because of changing python folder name form “Python3” to “Python” for older configs… Everything works correctly expect this debugger.
After resetting my computer problem come back.
You could try to diagnose whether something is not flipping the debug logging switch back off. I don’t know, some level of configuration that is overriding the one you’re at.