dsym file

It seems a few PhotoKit APIs have bugs where the completion handler is never invoked. I filed FB20407528: PHLivePhotoEditingContext.saveLivePhoto's completionHandler is never called for some Live Photos

Question1: Accessing deleted files via bookmark (Specification clarification) Our app saves file URLs as bookmarks, which file that user has selected on Files App or app-created, so to open a file which user has modified previously in the next launch. As a side note, you may want to take a look at this post which describes a longstanding issue which makes bookmark resolution much less reliable than it would be on macOS. When a user deletes a file in Files App (moves a file to Recently Deleted), the app can still resolve the bookmark and access the file for read/write operations. Is this behavior intended? In other words, is it correct that a bookmark can access a file that has been deleted in Files App but not permanently removed? Yes. Bookmarks are a relatively low-level file system construct compared to the Recently Deleted concept Files.app presents. As far as the bookmark system is concerned, it's j

This is most likely a PhotoKit framework bug and not a problem in your code. The native picker works because it bypasses the same broken code path. Implement defensive timeouts and fallbacks to protect UX while waiting for Apple to fix it. Here are some workarounds you can try right away: Add timeout logic - Cancel stuck requests after 30s and retry or show error Use PHPickerViewController - Modern API that handles iCloud downloads more reliably Implement fallback - Try requestImage instead of requestImageDataAndOrientation if first attempt fails Pre-check assets - Use PHAssetResource to verify local availability before requesting If that does not help, please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem. Also, please include a sysdiagnose, reference threads 806349, 732820, 113692. Post the Feedback number here after you have filed a bug. I'll check the status next time I do a sweep of forums posts where I've suggested bug rep

@88maxwell_booknet Please file a Feedback report about your issue, then post the number here.

I think it's worth a feedback report to request better treadmill integration in HealthKit. Do you have a feedback report yet? If not, would you mind to file one and share your report ID here? Also, does it make sense for you to store elevation data as altitude points in the workout route, assuming your app can grab the elevation data from the treadmill? Best, —— Ziqiao Chen  Worldwide Developer Relations.

Once you open the Feedback Assistant Ticket report, please post the FB number here for @App Store Commerce Engineer reference. If you have any questions about filing a a report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.

@barnabaskordas From Add your Icon Composer file to an Xcode project: If you create your Icon Composer file outside of Xcode, you can add it to your Xcode project anytime to view your icon in Simulator and on real devices. Just drag the Icon Composer file from Finder to the Project navigator, and Xcode provides feedback on where to drop it in a target folder. Alternatively, choose Add Files from the Add button at the bottom of the Project navigator and select your Icon Composer file in the dialog that appears. In the project editor, select the target and the General tab. Under App Icons and Launch Screen, ensure that the name in the App Icon text field matches the name of the Icon Composer file without the extension. You can have multiple Icon Composer files in your project but only one that matches the name in the App Icon text field. For an example, see the Configuring your app to use alternate app icons sample code.

The following console log says that your app detected an account switching at the beginning of the launch process, which may erase the existing data created before the switching. It also says that you were using a simulator. CoreData: warning: CoreData+CloudKit: -[PFCloudKitSetupAssistant _checkUserIdentity:]_block_invoke_3(1487): : CKIdentity record has changed from _b09f3f2b1357d21fdd823f58762f6077 to _4e8dc229775b034192825a3081a709a4 error: CoreData+CloudKit: -[NSCloudKitMirroringDelegate _performSetupRequest:]_block_invoke(1242): : Failed to set up CloudKit integration for store: (URL: file:///Users/yuanping_ke/Library/Developer/CoreSimulator/Devices/BA9191E9-6DB4-4A30-9196-0A6C06A11F2E/data/Containers/Data/Application/5977FE0D-50D4-4AE0-8134-5D8B0B662298/Library/Application%20Support/default.store) Later your app did successfully set up CloudKit integration, as shown below, and then did several successful exports and imports, but it seems that there is no change merged into the store. CoreData:

You should check the SF_DATALESS flag. See: TN3150: Getting ready for dataless files | Apple Developer Documentation

Hello @Jir_253, Please use Feedback Assistant to report any issues, request enhancements, and provide feedback on the Enterprise APIs for visionOS. If you're posting on the forums, it's helpful to provide the relevant FB number here so that we can take a look. If you're not familiar with how to file feedback requests, take a look at Bug Reporting: How and Why? We've sent you a new license file that is valid through November 1, 2026. Let me know if you have any additional questions, Michael

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()