dsym file

Hello psco, For further investigation of this issue, could you please file a bug report? Feel free to copy over the same information you've provided from this thread to it. Please see this guide for more information: Bug Reporting: How and Why? With a bug report in Feedback Assistant, you'll be able to track the status of the issue directly. You can also add attachments such as sample code and documentation of the issue (screenshots, videos, etc.). I'll make sure it gets to the relevant engineering team. Please don't forget to include the iOS version and device information in the report. Once you open the bug report, please post the FB number here for my reference. Thank you for your patience, Richard Yeh  Developer Technical Support

The files, both user-selected and sidecar, reside in a folder inside my user’s document folder, and I try to read the sidecar when the user opens the audio file. OK. SO, one thing I would test here is what happens if you test the same code with files that are in a directory outside of the normal user hierarchy. You can try with a directory inside your home directory, but I actually suggest using a folder ENTIRELY outside the user hierarchy— for example, on a disk image or an external volume. The issue here is that macOS has multiple independent systems of data protection, most of which are focused on user data (like the contents of ~/Documents/). Moving outside of that hierarchy means you’re looking at the basic case, which is easier to evaluate. Looking at the other cases here: I can access the sidecar file from the terminal and load its content. FYI, Terminal.app is a tricky tool to test an experiment with. The issues here are: It's not sandboxed, which exempts it from th

Hi, Thank you for the reply, here is more information: This AASA file is already running for many years. it's at&t AASA file, it can be found here: https://www.att.com/.well-known/apple-app-site-association I recently added the appclip section: appclips: { apps: [7QP83HJ33U.com.att.numverify.clip] } and a universal link addition (which works fine, the only problem is launching the app clip via URL in notes app): { appID: 7QP83HJ33U.com.att.numverify, components: [ { /: /numverify/appclip/* } ] } According to https://app-site-association.cdn-apple.com/a/v1/www.att.com) it is already updated in Apple CDN. I have reinstalled the app clip multiple times since then. Here is what I found in swcutils_show.txt file that is related to the app clip: Service: appclips App ID: 7QP83HJ33U.com.att.numverify.clip App Version: 2.0 App PI: { v = 0, t = 0x8, u = 0x914, db = 22E62DAB-9CF1-485C-A697-006229CE874E, {length = 8, bytes = 0x1409000000000000} } Domain: ***wwwdotattdotcom was written her

FYI, things work better if you just reply to the thread instead of using comments. Honestly, the comment feature doesn’t really work. First, let me start with the error messages you posted: Thank you. Yesterday, I accidentally removed arm64e from the compilation architecture and kept only x86_64 and arm64 architectures. The problem of Domain=NSPOSIXErrorDomain Code=8 Exec format error was solved. One thing you need to be careful about when looking at our log messages is focusing too much on the EXACT error code/detail instead of the overall flow. Looking at this message as an example: KernelManagerd: Error Domain=NSPOSIXErrorDomain Code=8 Exec format error This format structure: Error Domain= Code= ...is a common structure used by NSError to describe error codes from lower level subsystems. In this case, it's saying this was a POSIX error code, meaning error code 8 from the ERRNO range, or ENOEXEC. The string Exec format error is actually the generic POSIX error string description returned by perror(). All

@tansch, thanks for sharing that link. I'm curious, is your device managed by an IT department or other network admin that would have modified the hosts file like that? — Ed Ford,  DTS Engineer

@Dardikman I have an app clip installed via TestFlight. My AASA file is configured correctly (per 'Domain Status' in TestFlight). I want to be able to run the app clip flow (app clip card showing and app clip card launched) by invoking UIApplication.shared.open(url) from a different app, or by pressing the URL from notes app. Launching the App Clip experiences you configure for testing through the TestFlight app doesn't show an App Clip card. To view the App Clip card, register a local experience on your test device. For more information, see Test invocations with a local experience and Create App Clip experiences for testers in TestFlight. To launch your App Clip from another app, see Launching another app’s App Clip from your app.

Fixed this. In my main App target from the template, it defaults to - productType = com.apple.producttype.application.messages; in the project.pbxproj file. It needed to be - productType = com.apple.product-type.application;

@nemecek_f This is a known issue that is currently being investigated. If you have already filed a bug report for this issue, thank you. If you have not filed a bug report for this issue we encourage you to do so via Feedback Assistant (https://feedbackassistant.apple.com). For more information on Feedback Assistant, please visit https://developer.apple.com/bug-reporting. By filing a bug report, you’ll be able to track the issue, update Apple Engineering with additional information, and get notified of problem resolution

Thanks for the post. I would like to ask you more information about the AASA file and where is stored as well as when the app is installed in your device is when the AASA file gets downloaded and installed/registered. You can go over the troubleshooting guide and get the logs from the swcutil.txt file inside the sysdiagnose wil give you the information. Please check the Tech Note at TN3155: Debugging universal links | Apple Developer Documentation#Debug-through-sysdiagnose While the AASA file verification in TestFlight confirms your entitlement to handle App Clip URLs, the system might not always behave identically to a production-released app clip, please test with the Notes app. Ensure that your AASA file is correctly configured for your App Clip and can be found when calling https:///.well-known/apple-app-site-association in all your tests (you said this is working OK). The AASA file tells iOS which URL paths are associated with your app clip. iOS does

Hello, can you please elaborate on this: Apple gives me a certificate bundle of 1024-bit certificate. What is the size in bytes of fps_certificate.bin? Do you only see a single RSA-1024 certificate in the file?

[quote='874018022, Retouch, /thread/813562?answerId=874018022#874018022, /profile/Retouch'] The error … is just a symptom. [/quote] Right. But: We’re not 100% sure whether it’s a symptom of a bug in your code or a bug in the OS. Even if it’s the latter, the proximity of this error to that failure is useful diagnostic point. My suggestions above should allow you to rule out this being a bug in your code — or at least an ‘obvious’ bug — and generate diagnostic information that will be useful for Apple’s network engineering team to investigate. Now, if you want to file a bug about this now, that’s cool. However, my experience is that weird networking bugs get more traction if you: Provide clear evidence that the issue originates in the system, as opposed to your code. Include a sysdiagnose log with NE logging enabled. Note If you do file a bug, please post the bug number, just for the record. [quote='874018022, Retouch, /thread/813562?answerId=874018022#874018022, /profile/Retouch'] My concern