On Tue, Oct 28, 2014 at 12:51 PM, andrew mcelroy <[email protected]> wrote: > This tends to be a problem around major OS upgrades. > I see you have been down this road before.
Yeah. The "new default" font color change of 2012 (iOS6?) which left my app with black on black buttons. So much for (trusting) convention over configuration. The new "all your integers must now be longs" "lets force 64-bit everywhere" initiative last year that they only decided to email developers about two weeks ago. This didn't actually break my app but caused Xcode to throw up about 8,675,309 warnings I couldn't stand to look at. The change in iOS8.0 which caused the applicationDidEnterBackground callback in AppDelegate.m to no longer fire. That screwed me over hard :( The recent change in iOS8.1 where LocationManager no longer asks for permission it's damn self and just silently fails. Part of the fix required manually modifying my .plist file to add two new string constants for the new alert I have to manually invoke, I nearly died from it. Many times I've scrambled to get a fixed up release shipped only to wait 7-9 days for them to approve it. Releasing is slowest when you need it most. And Swift, same API, new syntax, brilliant! I'm currently refusing it exists. -- Greg Donald -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
