eskimo

In my experience debugging authorisation plug-ins is way too hard to attempt in the DevForums context. If no one else chimes in, I recommend you open a DTS tech support incident and I, or on of my colleagues, can help you out there.ps One tip: make sure your window can become ‘key’, that is, it returns YES for the canBecomeKeyWindow property. If that’s not happening by default, you can fix it with with a (trivial) subclass of NSWindow. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Have you tried mounting the volume at a location inside your app’s container?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

The column on the left, the one that toggles between hex and decimal when you click it, is the address of the memory being displayed. Consider the following pseudo screen shot.600000001550 F0290000 01000000 00201E00 00600000 ................ 600000001560 80040A00 00600000 00000000 00000000 ................600000001550 is the address of the byte whose value is F0, 600000001551 is the address of the bytes whose value is 29, and so on.The reason why you’ve not seen a lot of discussion of this is that:to folks who are used to assembly-level debugging this is really obviousfolk who are not used to assembly-level debugging rarely look at a raw memory viewI am finding one of these Line Offsets being referenced by one of my pointers, and it actually causes a bus error, so I'm trying to figure out how this could have happenedIt’s very likely you have some sort of memory management problem. My standard advice for debugging those is:use ARC (or Swift) everywhereenable all the compiler warnings and fix anything that it c

It doesn’t match the exact example you posted, but a guard statement (new in Swift 2) is often what you want here. func varnishWaffles(waffle: String?) { guard let waffle = waffle else { print(No waffle )-:) return } ... work with waffle, which is of type String ... }Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

[This is essentially a restatement of things I’ve said earlier but I want to make sure that it’s visible to folks just joining the thread.]To reiterate, I think the behaviour exhibited by the current iOS 9 beta is unacceptable, and I’m hopeful that things will improve before GM. Alas, I’m not in a position to discuss The Future™, even the near future, so I can’t post specifics right now.I realise this represents a serious level of uncertainty for you guys and I apologise that I can’t clear that up immediately.I will continue to update this thread as things evolve.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Thanks eskimo, you saved my day!!! 🙂

if a user reboots their phone, but doesn't launch my app, is it going to be able to refresh?The “has the user launched this app” flag persists across restarts.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I’m out of suggestions here. If no one else chimes in, I recommend you open a DTS tech support incident and I, or one of my colleagues, can help you in a more formal context.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I can’t see anything wrong with the code you posted but it’s easy to miss stuff in this sort of situation.What stream events do you see? You can work that out by putting log statements in -stream:handleEvent: on both the client and server. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

My dev server uses a self-signed certificate ….Just FYI, that’s a bad idea because it’s very easy to leave this debugging code in your app, and thus ship insecure software to your end users (some surprisingly well-known app developers have made this mistake!). A better approach is to create a development certificate authority and install that CA’s root certificate on your device. That reduces the code you need to write and ensures there will be no security mishaps.Technote 2326 Creating Certificates for TLS Testing explains how to do this.I'm not able to get past the CFNetwork SSLHandshake failed (-9824) error [because] the delegate are never called.Your App Transport Security dictionary is a little wacky. The keys you’re using are not the ones documented in the App Transport Security Technote.Also, if you have NSExceptionAllowsInsecureHTTPLoads set, you don’t need to set anything else. OTOH, if you follow my advice and use a custom CA you might be able to avoid having an ATS dictionary at all (although it’s

Is changing the keysize not supported or recommended at all?Correct. Changing global system preferences based on information you find in the Darwin open source project is not the path to long-term binary compatibility and is most definitely not supported.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Let’s try a simple test first: if you create a branch new OS X playground, set it to the following program, and then show the Assistant Editor, what do you see?println(Hello Cruel World!)I tried this on Xcode 6.4 and the Assistant Editor showed the printed text.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Internally, -initWithContentsOfURL: calls +[NSData dataWithContentsOfURL] to fetch the data to parse. Try calling that yourself to see if you get back the XML data you’re expecting to get back. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

[bran sent me his non-standard crash log via email.]The crash log shows that the backtrace was from iOS 9.0b5. By pulling apart _dispatch_queue_wakeup_with_qos_slow on that release I was able to see that this is a dispatch ‘object resurrection’ crash caused by a call to dispatch_retain on the queue itself. Two things to note here:A crash like this would leave a really helpful breadcrumb in a standard crash log but, alas, that information was lost by the custom crash reporter that you’re using.A standard crash report would allow me to check whether this is a common problem or not. Alas, custom crash reports make that hard.At this point I’m out of suggestions for how to debug this further. It’s likely that this is a queue ‘use after free’ problem within CFNetwork (or the underlying “tcp_connection” subsystem) but it’s hard to be 100%.I recommend you toss this into Radar; if you can figure out a way to reproduce the problem, that’d be ideal.Please post your bug number, just for the record.Share and Enjoy — Quinn

I think this is the droid you’re looking for.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com