eskimo

Thanks for the reply eskimo. Yes, I understand that the user explicitly consents to location through the dialog and can later revoke that. My point is why can't a pop-up be shown for access to Wi-Fi resources/information as well? I believe if the user consents and decent access was then available through the SDKs then a lot of apps would become possible on iOS again, such as network utility tools, Wi-Fi scanners and the numerous app examples given by others in this thread.I really think the consensus here is that yes, we fully acknowledge the privacy issues. However, given that there are privacy issues with location, photos, contacts, camera, etc that are all overcome with a pop-up dialog getting explicit user consent then can we please, please, please get a similar dialog that after getting explicit user consent then allows us to do some great things with Wi-Fi?

Because of the way NSUUID's are wrappers of CFUUID's in one of the most bizzarre nonsense toll free bridging that I have run across in Foundation …NSUUID is simply not toll-free bridged to CFUUID; the comments at the top of the header make that very clear.NSUUID's cannot be used as keys, stored in another containers for any extended period of time, or even subclassed.Subclassing is probably a bad idea, as it is for most Foundation primitive types, but the others should be fine. I played around with NSUUID a bit and didn’t have any problems with using it as a dictionary key or value. Perhaps you could post a concrete example of the problems you’re having?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

CSSearchableIndex:isIndexingAvailable appears to be undocumented right now.As always, if you find something lacking, please file a bug about it.Also, is it documented anywhere which devices are unsupported?Yes. Check out Which devices are these APIs supported on? in Technote 2416 iOS Search API Best Practices and FAQs.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Is there something special that AppKit NSApplicationMain() does that sets up the tracing?Not that I’m aware of, but certainly Crash Reporter understands the difference between apps and tools and might behave differently in each case.I would think dispatch_main would do the same.dispatch_main is nothing like NSApplicationMain. Specifically, it actually terminates the main thread, leaving your process in a state where it has no main thread! It does, however, have a main queue, which acts more like a standard dispatch queue rather than the way the main queue works in a run loop based process. I tried switching to CFRunLoopRun() …OTOH, CFRunLoopRun is much closer to NSApplicationMain. If you get totally stuck I recommend you open a DTS tech support incident and we can dig into this in more detail.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Your public key is malformed. Consider this:$ # I just put the hex dump into a file called tmp.asn1. $ $ hexdump -Cv tmp.asn1 00000000 30 81 88 02 81 80 d4 e7 f6 50 36 5c 80 bd 72 01 |0........P6..r.| 00000010 42 96 84 10 74 c4 97 67 ab 23 53 9f c5 b4 a3 a2 |B...t..g.#S.....| 00000020 e1 42 99 fe 48 42 72 92 24 75 2a 76 a5 a7 3a 62 |.B..HBr.$u*v..:b| 00000030 65 f5 5d 81 80 66 48 9a e1 83 43 5a ed c4 0e ba |e.]..fH...CZ....| 00000040 48 e5 3b 1a 84 d8 48 9b 17 e1 fa 11 6a c5 c4 0e |H.;...H.....j...| 00000050 cb f0 fa 4f c7 3c cf 4c ea 79 86 7b 82 59 bc a6 |...O.<.L.y.{.Y..| 00000060 00 f7 80 5c 8f a8 02 8e 63 52 35 4c cd 4f 18 62 |.......cR5L.O.b| 00000070 68 a8 f0 ae e6 92 bb 27 47 48 dc 35 00 ea c8 6f |h......'GH.5...o| 00000080 16 19 39 b2 c9 0f 02 03 01 00 01 |..9........| 0000008b $ $ # Now let's dump that file. $ $ dumpasn1 tmp.asn1 0 136: SEQUENCE { 3 128: INTEGER : D4 E7 F6 50 36 5C 80 BD 72 01 42 96 84 10 74 C4 : 97 67 AB 23 53 9F C5 B4 A3 A2 E1 42 99 FE 48 42 : 72 92 24 75 2A 76 A5 A7 3A 62 65 F5

--deep is almost never the right option for signing an app with nested code. You typically want to either have Xcode do this for you (which is what I recommend) or sign in multiple steps, signing nested code from the inside out. As to you overall problem, AFAICT your shipping nested code in an unsupported place. Dynamic libraries, like libcocoaprintersupport.dylib, should be in your Frameworks directory. See Table 3 of Technote 2206 OS X Code Signing In Depth. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Xcode is quite capable of signing a screen saver, or any other bundle for that matter. It has no high-level code signing UI for bundles, but you can tweak the code signing build settings directly. AFAICT you just need to set Code Signing Identity to Developer ID (CODE_SIGN_IDENTITY = Developer ID Application). Whether that resolves your Gatekeeper warnings is something you’ll have to test for yourself (I don’t spend a lot of time working on screen savers myself).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Actually it’s the opposite: there’s a connection without a valid outlet.UIKit is trying to load the nib (frames 4 through 6) and, as part of that, is trying to wire up the connection from ViewController’s someTextField property to some object (presumably a text field) within the nib. The problem is that ViewController has no someTextField property, or its not correctly flagged as an outlet. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Hi Eskimo, could you take a look at this?https://forums.developer.apple.com/message/38361#38361

Eskimo, thank you for your reply.It seems that you believe it is a regular behavior in a mobile device instead of a bug. My bug hypothesis is based on the observation that the same computation unit behaved differently on iPhone4S IOS 8.1.1 and on iPhone6 IOS 8.4.Although you gave your hypothesis, still there are a few observations that cannot be explained:1. The computation time of the same code on iPhone4S IOS 8.1.1 (check iPhone4s.ios8.1.1.log) is consistent, always use 0.074 seconds.2. On iPhone6 IOS 8.4, the first loop to do the computation requires 0.107 seconds. The computation time will decrease to the expected value (0.031 seconds) after a few more loops. If starting over again, it will repeat the same pattern. thermal (the system slows down the CPU as it gets hotter) should not apply here.Bug or not bug may be verified by running the same code on iPhone6 with IOS 8.1.1. Since I can't restore my iPhone6' IOS back to 8.1.1, I can't verify that. Maybe the next IOS version can give some hints.In

Hi Eskimo,Why the public key can generate in iOS 8 SDK? I used Base64 encode decode for exponent & modulus.Please enlight me.Best Regards,Chris

Are you sure you want to use WebSockets for this? Obviously I can’t see insite the app you mentioned, but most apps download using straight HTTP/HTTPS, avoiding WebSockets entirely.iOS has no WebSocket API, although there are there are third-party WebSocket libraries available. However, most apps download using NSURLSession. The advantage of NSURLSession is that you can download a resource while your app is in the background (or even terminated).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Is there a way to change this note by developers in Xcode?I knew I’d seen this before somewhere but it took me a while to find it. There was a thread about this on the old DevForums.That pointed to a bug (r. 20170304) which pointed to another bug (r. 18023555) which indicates that this is fixed in Xcode 7. And lo!, it is. The Notes field from the Document slice of the Identity inspector ends up in the <note> element within the XLIFF. For example: <trans-unit id=KZR-8E-61i.title> <source>Varnish</source> <note>Class = NSButtonCell; title = Varnish; ObjectID = KZR-8E-61i; Note = This button varnishes the selected waffle.;</note> </trans-unit>IMPORTANT If you’re working on OS X, make sure you set the note on the cell (NSButtonCell, NSTextFieldCell, and so on) rather than on the object itself. It’s the cell that gets exported to the XLIFF, so if you put the note on the object it doesn’t appear in the XLIFF.iOS doesn’t have (the madness that is ;-) NSCell, so this isn’t a

Our experimentation shows that for some reason, setting NSExceptionRequiresForwardSecrecy will also relax the requirement for SHA1 over the certificate chain.This is, alas, a bug. See this thread for details.This will cause careless developers to try and disable cert verification altogether, to make their apps work in the interim.I think you’re under the impression that disabling ATS disables all HTTPS server trust evaluation. That’s not true. Even if you set NSAllowsArbitraryLoads, which disables ATS entirely, you still get standard HTTPS server trust evaluation as it was done on iOS 8. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I can do this by [details of wildly unsupported technique removed]. Will Apple allow me to submit app to Appstore as there is no public api to get signal strength.?What you propose is completely unsupported and not appropriate for an App Store app.At this point in time, 7 years into the evolution of the iOS SDK, I think it’s safe to assume that the lack of an API to get the cellular signal strength is not an accidental omission but rather a deliberate policy decision. Attempting to hack around this restriction will not end well.In fact, this thread is a perfect example of how such hacks typically pan out: the unsupported approach described by nissolution in their original question stopped working in iOS 8.3 due to sandbox hardening.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com