We are unable to process your request

Yeah hard-coding *****. I don't use autolayout, but I position subviews relative to each other and the screen. For certain layouts the 'shorter size' of 3.5 inch iPhones doesn't get in the way but sometimes it does. If you start designing from the smallest screen size and work your way up...you should be alright, but then you won't be taking advantage of the larger screen sizes...you're just blowing everything up. I have a class that returns a screen type. When the 3.5 inch iPhone's aspect ratio gets in my way, I typically do something like-(void)viewDidLayoutSubviews { [super viewDidLayoutSubviews]; if (self.screenType == IPhone4ScreenType) { //alternative layout or constraints for different aspect ratio. } else { //Layout or constraints for everyone else. } }While using math for layout is useful, I wish Apple would have innovated a bit more on this. It would be nice if Interface Builder provided a solution geared more toward handling alternative layouts...instead of just giving us a square box to tinker wit

I tried this several times, but the watch just reboots and again gets stuck on the Apple logo. I have requested mail-in service from Apple a my watch is in a non-working state and it seems I can not do anything to fix it. Thanks for your help.

Feel free to file a bug/feature request if you'd like an alternate access path.My money is on it being over the horizon, if at all, as far as us avg. devs are concerned.

What you may not grasp is that Cocoa's traditional error handling rules are still in effect:If a method fails and there's only really one failure case for it (trying to convert a non-numeric string to a number, etc.), the method returns nil or false.If an operation fails because of some complex issue with the current state of the computer (no such file, Wi-Fi turned off, etc.), the method emits an NSError. In Swift, NSErrors are handled with the do/try/catch mechanism.If an operation fails because the programmer wrote code that did something invalid (out-of-range array index, etc.), the method fails an assertion or raises an exception, which you should generally allow to crash your app. In Swift, it's not possible to catch exceptions.Creating a fetch request with an inaccurate entity name falls into that third category: failures that can only be the result of programmer error. Such problems are still handled by failing an assertion and crashing your app.

I paid and now it tels me it is unable to verify my identity whenever I log in

>i just didn't know like for really simple questions if I should post that here too?Why not - that will help you to learn the process so you can ask better questions as you progress, and understand how things work here in the future. Do you best to use the right forum etc. In the mean time, be sure to search first and do your best to ask in the right topic area(s).◅▻

I wouldn't worry quite yet. Give it some time to process, especially with the recent changes to the unified developer program. Has been a long time since I registered for iOS (7 yrs), but I seem to remember it took a day or so for the login to be fully live, and that something was mentioned to that effect in the confirmation email. If you can't access the developer resources after 24 hours, then I would contact support and have them look Into it. But go ahead and do that earlier if you want peace of mind. They are usually very helpful.