It will be time consuming, but breaking the issues down one by one is the way to go. On the bright side, I'll likely find out a few things I didn't know, which is always a positive I my book.
"My Break-Dancing days are over, but there's always the Funky Chicken" -- The Full Monty > On Nov 10, 2015, at 1:55 AM, Quincey Morris > <[email protected]> wrote: > >> On Nov 9, 2015, at 20:26 , Lorenzo Thurman <[email protected]> wrote: >> >> So my question to the group should be obvious: >> Is there something I’m missing in my build configuration? Are there issues >> with Xcode 7 and deployment targets? > > I don’t know, but the one thing that is predictably different about using > later SDKs is that there are a few Cocoa APIs that behave differently when > you app is linked with different SDK versions. In theory, you keep track of > this by reading OS X release notes, which detail the new behaviors as they > are introduced. > > In a related vein, it’s also possible that you’ve been *misusing* APIs, and > it just hasn’t mattered before. I’m not saying I think this is likely, but > it’s something to keep in mind. In particular, it’s easy for memory > management problems in your app to be masked by unlucky timing across > multiple OS versions, until they suddenly show up in a new release. > > My suggestion is to try to reduce each problem you know about to a test > project that demonstrates the problem. (Failing to enumerate devices sounds > like it ought to be fairly easily reproducible.) In the course of doing that, > you may discover what’s going on, or if not you have good supporting evidence > for a bug report.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
