<!--
{
  "availability" : [
    "iOS: 10.3.0 -",
    "iPadOS: 10.3.0 -",
    "macCatalyst: 13.1.0 -",
    "macOS: 10.12.4 -",
    "tvOS: 10.2.0 -",
    "visionOS: 1.0.0 -",
    "watchOS: 3.2.0 -"
  ],
  "documentType" : "symbol",
  "framework" : "CoreData",
  "identifier" : "/documentation/CoreData/NSManagedObjectContextDidSaveObjectIDsNotification",
  "metadataVersion" : "0.1.0",
  "role" : "Global Variable",
  "symbol" : {
    "kind" : "Global Variable",
    "modules" : [
      "Core Data"
    ],
    "preciseIdentifier" : "c:@NSManagedObjectContextDidSaveObjectIDsNotification"
  },
  "title" : "NSManagedObjectContextDidSaveObjectIDsNotification"
}
-->

# NSManagedObjectContextDidSaveObjectIDsNotification

A notification that posts after a context finishes writing changes.

```
extern NSString * const NSManagedObjectContextDidSaveObjectIDsNotification;
```

## Discussion

This notification’s `object` is the saved context. Don’t peform any asynchronous work or block the calling thread. [`NSManagedObjectContext`](/documentation/CoreData/NSManagedObjectContext) posts notifications to the same thread that creates it.

The `userInfo` dictionary contains the identifiers of the inserted, updated, deleted, and invalidated managed objects. For the keys to access those objects, see [`NSManagedObjectContext.NotificationKey`](/documentation/CoreData/NSManagedObjectContext/NotificationKey). It’s safe to capture the dictionary’s contents.

Use this notification instead of [`NSManagedObjectContextDidSaveNotification`](/documentation/CoreData/NSManagedObjectContextDidSaveNotification) if you intend to process the changed managed object on a different thread. It’s safe to pass instances of [`NSManagedObjectID`](/documentation/CoreData/NSManagedObjectID) across thread boundaries.

---

Copyright &copy; 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)