eskimo

I'm not sure I understand your question. Are you asking about Apache running on 10.10? Or Apache running on some other system with 10.10 as the client? If so, what system is that?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I read somewhere that many of the core GUI frameworks don't work because they all check the user's preferences for the default font size, locale, etc. so they won't work until the user's home directory is mounted.That may be true (never tried it myself) but it's irrelevant to an auth plug-in because the auth plug-in's code runs as _securityagent.Is your final goal to create an SFAuthorizationPluginView or to display content in your own window? That matters because, in the latter case, you have to make sure to set canBecomeVisibleWithoutLogin on your window. In the former case your view shows up in a window managed by the system, which already has that property set. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

At the moment I am just recieving the nil every time.Where are you seeing this nil? I see you have a bunch of println statements; presumably one of these is seeing a nil value.btw For situations like this, where there are multiple processes in play, I generally recommend NSLog. That way you can see the output of all the processes in one place (the system log displayed in Xcode's Devices window).I assume this is because the app doesn't have time to load all of the objects into the array from parse before it tries to pass it back to the watch?You haven't really describes how this asynchronicity fits into your app's structure. Does DataManager.sharedInstance.loadRides work asynchronously? If so, then yes, it's clear that the reply going back to your watch app could have stale data because it just sends back the current state of affairs, not the state after the async work has finished. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail

So I made a new Xcode project to test it out but now whenever I press a key it just makes the bong sound. Any idea why that might happen…I'm not sure what's going on in your case but I tried this with a simple test project and it worked as expected. Here's what I did:I created a Swift project from the Cocoa Application template.I created a test view class as shown below.import Cocoa class TestView: NSView { override var acceptsFirstResponder: Bool { get { return true } } override func keyDown(theEvent: NSEvent) { NSLog(down) self.acceptsFirstResponder super.keyDown(theEvent) } override func keyUp(theEvent: NSEvent) { NSLog(up) super.keyUp(theEvent) } } I added an instance of this class to my nib and wired up a reference to it from my app delegate.In my app delegate I called -becomeFirstResponder on it.I ran the app and pressed keys. Both down and up were printed.2015-08-03 09:29:32.480 xxy[90211:8432000] down 2015-08-03 09:29:32.578 xxy[90211:8432000] up 2015-08-03 09:29:32.914 xxy[90211:8432000] down 2015-08

Hello eskimo 🙂I did the following:class MainViewController: NSViewController { override func viewDidLoad() { super.viewDidLoad() } override func keyDown(event: NSEvent) { if (event.keyCode == 1){ print(down) } } override func keyUp(event: NSEvent) { if (event.keyCode == 1){ print(up) } } }I put that in my view controller. Was that wrong to do? Because when I do it the down arrow key works but the up arrow key doesn't. But then if I do exactly the same thing in a new projet it doesn't work.

Did you notice that eskimo included the following method in his code?override var acceptsFirstResponder: Bool { get { return true } }Unless you include this one, then your view cannot respond to key events.

I'm looking for getting list of nearby wifi's SSID, without connecting to it.It's not possible to do this in any general way. There are some affordances for specific use cases (for example, apps can use the External Accessory framework to set up MFi accessories that have a Wi-Fi) but no general-purpose 'scan for nearby Wi-Fi networks API.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Yes in particular I wish for the extension to communicate with the sandbox containers localhost:9339.What API are you using to run this communication? NWTCPConnection?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

The critical issue here is Wi-Fi auto join. Let me explain…iOS fully supports multiple network interfaces but there are some non-obvious interactions that you have to be aware of. Specifically, when iOS tries to auto join a Wi-Fi network, it probes the network to see if its functioning. If it's not, it disassociates from the Wi-Fi, leaving the default interface set to WWAN.This disassociation does not happen when the user manually joins the network.So, you have two choices here:If you configure your Wi-Fi network to satisfy the auto join probe, then iOS will switch the default route to Wi-Fi. WWAN stays up and is used by critical system services (like push notifications), but most apps will switch to using the (dysfunctional) Wi-Fi.In this environment you can write code to run your network requests over WWAN but you'll have to use low-level APIs because our high-level APIs don't have a way to force a request to run over WWAN.If you configure your Wi-Fi network to not satisfy the auto join probe, iOS will not

This is not easy. The problem breaks down as follows:file URLswell-known network URLs (http, https, ftp, and so on)other URLsFor other URLs there's obviously no general-purpose solution; you'll have to handle these on a case-by-case basis or simply treat them all as external.For network URLs, the first problem is one of definition. If the network URL points to a server that's running on the local machine, is that internal or external? If you consider it external, you're done: all network URLs are external. If you consider it internal, you have more work to do. You could resolve the host to see if the resulting IP address matches one of the machine's local IP addresses, but that starts getting really ugly really fast. A host can resolve to multiple IP address (and don't forget that some might be v4 and some might be v6), so what do you do if you get conflicting answers?For file URLs the problem is, again, one of definition. The file URL might point to a file server, in which case you want to treat it like a ne

I've filed an issue as well: 22127901Thank you.Is there any indication of when this might be addressed?Which issue specifically? There's a bunch of related issues covered by this thread, all of which have workarounds, although some are less satisfactory than others.However, as far as future changes to the OS are concerned, that's not something I can speculate on; DTS Engineers aren't issued with a crystal ball, alas.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

My question is why is that DYLD_LIBRARY_PATH variable is not set by launchctl setenv, when I can set it for a dummy variable. This is the first time you've mentioned a dummy variable. Can you explain what you mean by that?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I'm refereing ot Apache running on OSX 10.10.OK. Is that the built-in Apache? Or a version that you've installed yourself?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

In the iOS keychain implementation errSecNotAvailable is returned for a bunch of reasons, mostly related to unexpected internal errors. I would not expect to see this as a result of you using the API incorrectly. Earlier you wrote:… does the user have to do something on the device to fix thisThat's my immediate suspicion but really I'm just speculating at this point. What's the context for your question? Are you seeing reports of this coming back from the field? When it happens, do you see anything interesting in the device's system log?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

There are still a couple of issues though. The first issue is that it only seems to work on a fast internet connection.Before you start trying to engineer the mechanics of that, you have to think about your user-level behaviour. Imagine that every network request you make takes a minute to come back? What should the watch be showing during that minute? Do you want to show a 'please wait' UI? Do you want to show the last data that was successfully fetched? And so on.Remember that most watch UI interactions are shorter than a slow network request, so you have to have a plan for handling this case.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com