eskimo

I’m not sure I understand your question but I’ll take a stab at the basics. There are two different strategies you can use here:Apple System Log (ASL) — See the asl man page for details.custom loggingIf you’re using ASL, it takes care of where the logs get written, so you don’t have to worry about that.If you use your own custom logging, you can put the log file anywhere within your app’s container, although Library/Logs/ is traditional. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

and crash on iOS 7.1 Simulaotor when using Xcode 6.4.In my testing it works with the 7.1 simulator if you target a 64-bit CPU (like iPhone 5s) but fails, as you’ve described, when targeting a 32-bit CPU.I suspect you’re being bitten by a limitation of $arg1, namely, that it always maps to a register. On i386, which is what the 32-bit simulator uses, parameters are passed on the stack, not in a registers, and thus aren’t available via $argXXX notation. Rather, you have to dump the stack and work things out from there. Here’s an example, assuming you’re stopped at the first instruction of objc_exception_throw: (lldb) po $arg1 error: use of undeclared identifier '$arg1' error: 1 errors parsing expression (lldb) # Dump 8 4-bit words in hex from the top of the stack. (lldb) m r -c 8 -s 4 -f x $esp 0xbff3454c: 0x007d5fbb 0x79c55090 0x008de3d0 0x000cc038 0xbff3455c: 0x79c55110 0x00000000 0x008dd82c 0x0091b940 (lldb) # The first word is the return address; the second is the first (lldb) # parameter, so dump that. (ll

First up, I moved your question to App Frameworks > Cocoa Touch because, while it’s not a great match, it’s much better than Xcode > Playgrounds.Second, with regards your requirements:i want make a specific Calendar app which can update date info in app icon, like iOS Calendar appthe answer is, no, there’s no way to do this. The Calendar app is built-in to iOS which has a special affordance for this feature.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

This really depends on how your project is set up. If you’re building all the frameworks from source via an Xcode workspace, Xcode should do the right thing here (have one framework that your app and all the other frameworks use). If you’re using some other technique, things get more complex.Regardless, it should be possible to fix this (assuming all the frameworks are binary compatible), it’s just a question of getting the packaging right.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

What should I do to make this app available to others without them needing to do anything else then typing their password?On OS X sudo is really designed for admin folks working at the command line; it’s not appropriate for writing apps. ahltorp’s suggestion of Authorization Services was a good one, but I’d extend that with a pointer to the EvenBetterAuthorizationSample (EBAS) sample code.I specifically recommend that you avoid AuthorizationExecuteWithPrivileges. It’s been deprecated for a while now and with good reason: the underlying privileges extension mechanism shown by EBAS, SMJobBless, ensures that the user grants the privileges that you request to your code, as opposed to some random, potentially malicious code. Finally, I moved your question to Core OS > Processes because this stuff is not Swift specific.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

The biggest issue I have with Swift today is the lack of support for atomics.Did you file a formal enhancement for this already? If so, what’s the bug number?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

jorisvervuurt wrote:It's been very silent on Apple's side...You call this silence (-:@eskimo, do you have an update regarding this […]No. As I mentioned earlier, I will update this thread when I have more to share.jorisvervuurt wrote:Another thing: 'deprecated' basically means it is going to be removed in a future version.And JetForMe wrote:I'd also like to point out that deprecation means an API is unchanged for now, but will go away in the future.Just on a personal level, I totally agree with your definition of the word “deprecated”.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I am terribly sorry if I offended you Eskimo, but the fact is that Multipeer doesn't work, in my opinion.We tried to use it in an Enterprise app and it works great with two devices. Not so good with three and anything above that it just falls apart.It's a great pity as the idea is good.I was hoping that with Swift 2.0 coming out there would have been some work done to make it more stable.No-one would be more happy than me if I could get it to work. I've tried to get it to work as a mesh, as it is supposed to work, but with no avail. Again, two devices work great, involve more and you're in for trouble. One suggestion (Apple) was that is you lost contact with a peer, to dump the MPC object and start again.Again, works great with two devices, but not so great with more.I need 8 devices talking to each other - please tell me it can be done!

There’s no single place in DevForums that covers all aspects of this question. I recommend that you break the problem down into subtasks and then ask separate questions for each one. For example, you can ask questions about accessing the camera over in Media / AVFoundation (Video and Camera.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

There is not enough detail here to even hazard a guess.First question, is this tied to the site or to your app? That is, if you create a small test app that holds just a UIWebView and load the same site into that, does it crash in the same way?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Not working here anymore […]I retested this on iOS 9.0b5 and it’s working as expected. Specifically:I wrote a tiny test program that fetches https://stanford.edu.I ran it without a NSAppTransportSecurity dictionary; the load failed (there’s a transcript of the error at the end of this email).I ran it with the NSAppTransportSecurity dictionary shown in my Jul 15 post; it worked.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com2015-08-18 08:29:26.310 QTestbed[7515:5780925] task start 2015-08-18 08:29:26.983 QTestbed[7515:5781012] NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9802) 2015-08-18 08:29:26.985 QTestbed[7515:5780925] task error NSURLErrorDomain / -1200

I have created a class extension for NSURLSessionConfiguration and NSURLSession that overrides dealloc is called, however it is not being called.That’s not a valid test. To cope with odd structuring requirements within the OS, NSURLSessionXxx objects are not straightforward Objective-C classes. You won’t be able to successfully subclass or extend them.Is that the only evidence you have that something is leaking? Or are you seeing the leak in Instruments as well?Finally, be aware that NSURLSession objects are intended to be long-lived. A common usage pattern is to create a single session object at app launch and have it persist for the duration of the app. Creating a new session object per request is needlessly inefficient. I’m not sure if you’re doing that for real or just to demonstrate this problem, but if it’s the former then I recommend that you change direction.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo

Is there a way to inplement the EvenBetterAuthorizationSample inside an application written in Swift?The only gotcha that I can think of relates to Swift’s runtime libraries. As I’m sure you’re aware, Swift apps include a a hefty set of runtime libraries. Normally that’s not a problem because Xcode configures every Swift image in the app to point to the same libraries. However, the technique shown by EBAS causes part of your app (the helper tool) to get copied from within your app to /Library/PrivilegedHelperTools. That will break the tool’s linkage to the Swift runtime. I’m not sure if there’s a good way around this.Is it possible to mix the code between C and Swift?Yes.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I’m confused. We discussed this issue in a thread in this very same topic area last week. Why did you create a second thread for this?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Thanks for the clarification.To answer your direct question, no, there’s no supported way that you can convince the crash reporter / iTunes Connect infrastructure to handle arbitrary error log files; it’s only supported use is crash reports.Now, you could make your app crash when it gets an error, but that’s probably not what you’re looking for.Alternatively you could build your own error log transport mechanism. Yes, that means you’ll need to ask for the ‘outgoing network connections’ entitlement, but there’s nowt wrong with that as long as you have a good reason.One thing you will have to be very careful about is user privacy. While I’m not qualified to advise you on how to resolve the potential privacy issues here, it’s clear that such issues exist.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com