SwiftData setup (modern persistence) in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the role of the @Model attribute in SwiftData?

In SwiftData, you mark your data model classes with @Model. What does this attribute do?

A It disables persistence for the class, making it transient only.

B It marks the class as a UI component to be displayed on screen.

C It tells SwiftData to manage the class as a persistent data model with automatic storage support.

D It converts the class into a network data transfer object.

💡 Hint

Think about what you want SwiftData to do with your data classes.

The @Model attribute tells SwiftData to treat the class as a persistent model. This enables automatic saving, fetching, and syncing of data.

❓ ui_behavior

intermediate

What happens if you forget to inject the ModelContext into your SwiftUI view?

You have a SwiftUI view that needs to save data using SwiftData, but you forget to add @Environment(\.modelContext). What will happen when you try to save?

A The app will crash at runtime with a missing environment key error.

B The data will save normally without any issues.

C The data will save but only locally, not persisted.

D The compiler will show an error and prevent building.

💡 Hint

Think about how SwiftUI provides the context to views.

If you don't inject modelContext, the view cannot access the persistence context. This causes a runtime crash because the environment key is missing.

❓ lifecycle

advanced

When is the SwiftData container initialized in a typical SwiftUI app?

In a SwiftUI app using SwiftData, when is the ModelContainer typically created and injected?

A Automatically by the system without any code needed.

B In the app's main struct, during initialization, before the first view appears.

C Inside each view's <code>onAppear</code> method individually.

D Only after the user logs in, triggered by a button action.

💡 Hint

Consider where you set up global app state in SwiftUI.

The ModelContainer is created once in the app's main struct (e.g., in @main) and injected into the environment for all views to access.

❓ navigation

advanced

How do you pass a managed SwiftData model object between views?

You want to navigate from a list view to a detail view showing a SwiftData model object. How should you pass the object?

A Create a new instance of the model object in the detail view.

B Pass only the object's ID and fetch it again in the detail view.

C Store the object in UserDefaults and read it in the detail view.

D Pass the model object directly as a parameter to the detail view initializer.

💡 Hint

Think about how SwiftData manages object identity and sharing.

Passing the model object directly keeps the same managed instance, allowing edits and updates to sync automatically.

🔧 Debug

expert

Why does this SwiftData save operation fail silently?

Consider this code snippet inside a SwiftUI view:

func saveItem() {
  let newItem = Item(name: "Test")
  modelContext.insert(newItem)
  // Missing save call here
}

Why does the new item not persist after app restart?

A Because <code>modelContext.save()</code> was not called to commit changes.

B Because the <code>modelContext</code> was not injected into the view.

C Because the <code>Item</code> model is missing the <code>@Model</code> attribute.

D Because the item name "Test" is invalid and rejected by SwiftData.

💡 Hint

Think about what final step is needed to persist changes.

In SwiftData, inserting an object adds it to the context, but you must call modelContext.save() to write changes to disk.