Invert guard let scoping

Another idea besides what @Erica_Sadun has already suggested is to simply check for the success case first. If error is non-nil, but the server still returns a 200-status and all the data you need, there is no reason to error out anyways as you do in the code you start the thread with. You can guard on the success case and return there instead.