Core Data is a powerful framework provided by Apple for managing an app's data model. It allows developers to manage the model layer objects in an application as well as manage object graphs and lifecycle. However, once Core Data is implemented, developers might wonder how to check what data is actually being stored in their Core Data database. This article will explore the ways you can inspect and interact with Core Data's stored data, providing both technical explanations and examples.

Exploring Core Data Storage

Core Data uses a persistent store to save records. By default, this is a SQLite database, though it can also be XML or binary. When working on an iOS simulator or a real device, you can locate and inspect these persistent store files to check what is stored.

Locating the SQLite Database

When using a simulator, Core Data's files are usually stored in your application’s sandbox directory. Here are the steps to locate them:

1. Find the Application’s Sandbox Directory:
   • Run your application on the iOS simulator.
   • Open Terminal and navigate to your project's path if needed.
   • List devices to get the simulator device identifier.
   • Navigate into the identifier corresponding to your running simulator and find the corresponding directory:
   • Multiple directories will be presented; locate the directory that contains your application's data.
   • Use `sqlite3` to open the Core Data SQLite database.
   • List all tables to see the entities.
   • To check the data stored, you can run SQL queries, like `SELECT`.
   • Set up a `NSFetchRequest` to retrieve data from Core Data.
   • Use breakpoints or `print` statements in Xcode to help in debugging and inspecting the fetched data.

• Core Data Editor: This is a graphical tool that allows browsing through Core Data databases.
• Core Data Lab: It provides a macOS application that can open and view Core Data files directly.
• SQLite Browser: Offers a general-purpose database tool for interacting with SQLite files.
• Always ensure you're working on a non-production environment while inspecting live databases.
• Implement and use unit tests that can confirm what data is being saved/modified.
• Regularly backup your database before making database schema changes or updates.
• Understand Core Data's limitations about relationships and data integrity.