Hi Richard, Thank you for the clear explanation and the suggested workaround. I understand now that there is no official API to fetch assets specifically from the "Recently Deleted" album, and that using UIImage to create a new asset would result in the loss of critical metadata. Regarding your question about our goals: Our intent was to provide a better UX by warning users before a save operation results in an "invisible" asset (due to the automatic grouping with deleted items). Since we cannot reliably detect this state via the current Photos Framework, we will evaluate whether to handle this by pre-processing the metadata or by filing an enhancement request through Feedback Assistant as you suggested. I appreciate your time and the technical insights provided throughout this discussion. Best regards, Jimmy

Hi Richard, Thank you for the guidance. I have tested fetchAssetsWithBurstIdentifier:options: as you suggested and confirmed that I can locate the assets sharing the same burstIdentifier even when they are not appearing in the main Library. Here is the core of the issue I’m facing: While I can fetch these assets, there is no explicit property on PHAsset to determine if it currently resides in the "Recently Deleted" album. In our app's workflow, PHPhotoLibrary returns success = YES during the performChanges block. However, because the new burst is automatically grouped with an existing deleted set, the photo is immediately invisible to the user in the main Library. Our intended UX is to show a warning alert to the user if we detect that a matching burstIdentifier already exists in the "Recently Deleted" album. This prevents the confusion of a "successful" save that results in an invisible file. Question for clarification: Is there a recommended, officially supported way to identify if a PHAsset returned by fetchAssetsWithBurstIdentifier:options: is currently in the "Recently Deleted" state so we can reliably trigger our UI alert? I appreciate your technical insights on how to handle this scenario properly to ensure a clear experience for our users. Best regards, Jimmy