The work around we use currently (Mac OSX Yosemite, iOS debugging via simulator, Safari for debugging) is to start steroids connect with the experimental "livereload" flow:
> steroids connect --livereload
Then we start the iOS simulator and Safari for debugging, go to the page we're debugging (in the simulator) and choose the same page from the Safari "Developer -> iOS Device" menu. E.g. if we're debugging the "login" view in simulator then we load the same page from the Safari debugger menu.
Once that has all loaded you can view the Console tab in the Safari debugger and then simply re-save your JS source file to re-load the view in the same location and without closing the debugger -- you can then use console.log to debug.
console.log('my error message here');
Not ideal but much better than having nothing currently with the logging not working.
P.S. also works for fiddling with the CSS styles and HTML within Safari dev tools