At this point, everyone is confused, including you. 😉
Nothing you've described as being an error message is, in fact, an error message.
>> So I get the "Thread 1: breakpoint 1.7" error at line 3 in this example.
This is displayed, in the source file editor, with a translucent green bar highlighting the line of text, when your app stops in the debugger at a breakpoint. It's not an error, just a breakpoint. If you look at the left end of the green bar, you should see a blue icon "pointing" at the line of text. That's a breakpoint icon. To get rid of it (assuming it wasn't your intention to stop here), drag it away from the margin of the text editor until the cursor changes to a "cancel" icon, then let go.
It's easy to set breakpoints by accident if you click in the margin of the editor. You should remove any other breakpoints you've accidentally set.
>> I get this error in the debugging console when I run everything: "VideoListTableViewController.init(coder : NSCoder) -> VideoListTableViewController?"
This isn't an error message either, it's just the name of a method, presumably the method that was executing at the time your app stopped at the breakpoint described above. It's not clear where you're seeing this, but I guess its in the toolbar that appears near the bottom of the Xcode window while the app is running, next to a blue icon, next to something like "Thread 1" with its own blue icon, next to your app name. Right? That's just a display of where you app was executing when it stopped (due to the breakpoint).
Note that, if you stop at a breakpoint, remove the breakpoint (by dragging it out of the editor margin), you can continue execution by clicking the Continue icon (3rd from the left on that same toolbar).
All this is basic Xcode usability stuff. There are a lot of controls and displays in an Xcode window. If you're not sure what they are, you really need to read through the Xcode documentation to get familiar with what's there.