NSCocoaErrorDomain Error Code 4

Never underestimate a bad cable as the possible reason. For some reason, since the beginning of iPhone, you can have a cable that's good enough to get through charging and sometimes syncing, but fails when doing restores and more sensitive tasks. A few tips:Make sure your device registered with the developer program's UDIDs.Make sure iTunes is up to date.Make sure your hosts file on your computer hasn't been modded.Ensure there's no dust or debris in the bottom of your device that may be blocking a solid connection.Try a different cable.Try a different computerAnd if all else fails, the apple store will usually try restoring it for you, even if it's OoW -- though if they also can't restore it, you may be looking at an Out of Warranty service repair.https://support.apple.com/en-us/HT204770Check your USB connectionsErrors: 13, 14, 1600, 1601, 1602, 1603, 1604, 1611, 1643-1650, 2000, 2001, 2002, 2005, 2006, 2009, 4005, 4013, 4014. You might also see a message that includes invalid response.If the USB connection

when I ran your code I saw the actual problem 🙂when creating the URL I needed to specifically create a file URL.//var torusModel = MDLAsset(URL: NSURL(string: path!)!) let torusModel = MDLAsset(URL: NSURL.fileURLWithPath(path!))Loaded just fine after that

The watchOS developer library has a PotLoc sample which is sample code for using CoreLocation. https://developer.apple.com/library/prerelease/watchos/samplecode/PotLoc/Introduction/Intro.html#//apple_ref/doc/uid/TP40016176In particular, use manager.requestLocation() and then implement the delegate methodoptional func locationManager(_ manager: CLLocationManager, didUpdateLocations locations: [AnyObject])

Adding a catch-all catch will let things compile:moc.performBlock { do { try moc.save() print(Success) } catch let error as NSError { print(Fail: (error.localizedDescription)) } catch { print(Fail: (error)) } }If you're not using the NSError, you may as well use just a single, generic catch.If you don't catch all possible errors, the throws propagates to the caller, in this case, performBlock. However, performBlock doesn't expect an error, so you must catch all possible errors, or you must call try!, unsafely, instead.The error isn't super friendly, so it may be worth filing a bug report to make it easier to understand.

Extremely common for early betas to abuse the battery - seems the power management code is kept out for a few and then brought in w/later betas.

birthday and party are two separate events and they both could be selected in a single entry and it doesnt reduce to a single event called 'birthday party'. Using this app called 'Core Data Editor' I found out that my code was only taking one event where multiple are selected. So my store didnt have any entry with two events Birthday and Party! I guess I found where the bug is.