dsym file

This looks like a problem with your curl command. Can you try the following? curl -d @Test_Inputs/iOS/spc_ios_hd_lease_2048.json localhost:8080/fps The @ symbol is needed to send the contents of the file. Otherwise, curl just sends the filename as a string in the body of the request, and the server will respond with that error. Also, it looks like you are running from the Key_Server_Module directory, so the relative path is probably Test_Inputs instead of ../Test_Inputs.

What Kevin said plus… It’s reasonable to use different approaches for different subsystems in your app. For example: If you’re fetching an audio file to play immediately, a standard session is probably best. Critically, it results in the least latency, which is important because you’re actively playing that audio. And while this requires your app to not suspend, that’s OK because you’re playing audio. If you’re downloading a large file that the user isn’t actively playing, a background session makes sense. If you’re scanning for updates, you could use a background processing task. This typically runs overnight, which is fine because the user isn’t expecting the results immediately. Unless they bring your app to the foreground and tap the refresh button, in which case you might run the same code immediately. And you can then use a continued processing task to complete the refresh. But that’s just one way to slice this. You have lots of options and it’s kinda up to you to decide which one make

[quote='873184022, iceboy, /thread/811084?answerId=873184022#873184022, /profile/iceboy'] The user previously … [/quote] Well, that’s quite an edge case. Having said that, just because it’s an edge case doesn’t mean it shouldn’t work |-: [quote='873189022, iceboy, /thread/811084?answerId=873189022#873189022, /profile/iceboy'] And what is the basis for generating this value? [/quote] I can’t go into those details. I don’t know off the top of my head but, even if I did, I’m reluctant to discuss implementation details like this unless there’s some specific benefit to it. And I’m not seeing that here. Rather, this is clearly something that you should report as a bug. IMPORTANT For this bug to get any sort of traction, you’ll need a sysdiagnose log. I’m presuming you can’t reproduce that yourself, so you’ll need to ask your user to either send you the sysdiagnose log or file their own bug, attach the log there, and send you the bug number. Ideally they’d trigger this sysdiagnose log immediately after the

Hey Quinn, thanks for all the material. I realize that I have a basic issue in my code. data is not loaded. In the previous version, archiver had a connection to data let archiver = NSKeyedArchiver(forWritingWith: data) That's no more the case, so data is empty, hence the problems. let data = NSMutableData() let archiver = NSKeyedArchiver(requiringSecureCoding: true) archiver.encode(myObject, forKey: theKey) archiver.encode(myObject2, forKey: theKey2) archiver.finishEncoding() do { try data.write(to: an uRL, options: []) // data is empty of course ! } catch { } So should I replace: archiver.encode(myObject, forKey: theKey) archiver.encode(myObject2, forKey: theKey2) archiver.finishEncoding() do { try data.write(to: anURL, options: []) // So object and object2 are on file with let data = try! NSKeyedArchiver.archivedData(withRootObject: myObject, requiringSecureCoding: true) let data2 = try! NSKeyedArchiver.archivedData(withRootObject: myObject2, requiringSecureCoding: true) archiver.finishEncoding()

What Kevin said, obviously (-: [quote='873111022, absinth, /thread/813148?answerId=873111022#873111022, /profile/absinth'] i just tried to reproduce it again … today the issue is gone. [/quote] Bah! [quote='873111022, absinth, /thread/813148?answerId=873111022#873111022, /profile/absinth'] so, unless the log files i already have are enough [/quote] That’s unlikely. A sysdiagnose log captures a bunch of state. That includes a system log snapshot, but it includes other state that’s not directly encoded in the log. The chances of a bug getting traction without that log is… well… it’s not impossible, but it’s significantly reduced. There’s a lesson to be learnt here, namely grab sysdiagnose logs early and often (-: If you don’t see the problem again internally, you can still ask your customers to take a sysdiagnose log themselves. It’s relatively easy for them to do. They can either pass it along to you or, if they’re not comfortable with that, file their own bug in Feedback Assistant and pass y

Xcode is telling you that com.apple.developer.shazamkit isn’t a real entitlement. See Determining if an entitlement is real for more background on this. The solution is to do what Xcode suggested, that is, remove that property from your .entitlements file. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

But the funny thing is, I just tried to reproduce it again because you requested the sysdiagnose logs and ... today the issue is gone. The helper now works just fine on this Mac too. This is speculative, but this is a kind of thing that happens when there are issues with the LaunchServices database. That database is how the system maps bundle IDs to file system locations, which can obviously be a problem if/when something goes wrong in the database. These issues often have exactly the kind of pattern you’re describing— something stays broken quite persistently, then suddenly starts working for no apparent reason. I have an extended post about this sort of issue here, however, the two points I’d pull from that post: While I've seen these issues happen to many developers, they're much, MUCH rarer on end-user systems. The unique dynamics of the development process are the single biggest factor here. The fact this keeps happening is a side effect of LaunchServices’ basic role, NOT a lack of attention or

Jumping in with some thoughts from the background execution side... The code that does this work has multiple URLSession callbacks, state information, and multiple error cases that need to be handled. The flow is a bit complex. I thought this functionality would be better implemented using a single code path with async/await. At this point, based on what I've learned here, it feels like async/await won't meet my needs because I want them to continue if the app moves to the background. No, I don’t think the async/await architecture itself is really a factor. Background execution operates at the process level, and, in general, a process that's awake works the same way a backgrounded process does. There are a few exceptions (notably, access to the GPU), but, in general, background execution issues are about keeping your app awake, NOT what it can do once it's awake. That's PARTICULARLY true of the audio background category. Expanding on what Quinn said here: Background audio is the most straightforward, at least

Thank you for posting in developer forums. To verify, what failure are you hitting? This is not a known issue and local testing is showing leaderboards for me. If you need to include sensitive information or logs you can always use feedback assistant to file an issue for the sdk.

please suggest any public api's for the same or any chance to use this private api. I'm not aware of any public API for this. All I can really suggest is here is that you file a bug describing exactly what you're trying to do, why you're trying to do it, and asking us to provide API. Please post the bug number back here so I can ensure that it's properly routed. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Thanks for the post. Yes, absolutely. Your understanding of the situation is largely correct, and this is a very common point of confusion and frustration when working with Universal Links, WebViews, and OAuth flows in iOS. I have indeed developed mobile apps that extensively use Apple App Site Association (AASA) and Universal Links in iOS, and I've encountered this exact scenario many times with browsers that are not safari. I always recommend to test using the iOS Notes app to see if the app its open correctly. Universal Links are primarily designed to work when a link is opened from a system-level context (Safari, Mail, Messages, Notes, or any app that explicitly asks the OS to open a URL, like UIApplication.shared.open(url)). When a WKWebView (or UIWebView for older apps) attempts to navigate to a Universal Link URL, the WebView itself is acting as a miniature browser. It does not automatically hand off the URL to the iOS operating system for Universal Link resolution. Instead, it tries to load that URL i

@nagy.katalin@codespring.ro Please file a Feedback report with a sysdiagnose file, then post your Feedback number here.