@State property wrapper in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What happens when you tap the button?

Consider this SwiftUI code snippet using @State. What will the Text display after tapping the button once?

iOS Swift

struct ContentView: View {
  @State private var count = 0
  var body: some View {
    VStack {
      Text("Count: \(count)")
      Button("Tap me") {
        count += 1
      }
    }
  }
}

A The Text updates to show "Count: 1"

B The Text stays at "Count: 0" because @State does not update UI

C The app crashes because count is immutable

D The Text shows "Count: 0" but the button becomes disabled

💡 Hint

Remember that @State allows the view to update when the variable changes.

The @State property wrapper marks the variable as mutable state for the view. When the button increments count, SwiftUI re-renders the view and updates the Text to show the new value.

❓ lifecycle

intermediate

Where should @State variables be declared?

Which of these is the correct place to declare an @State variable in a SwiftUI view?

A Inside the body property of the View

B As a private property inside the View struct, outside the body

C In the AppDelegate class

D Inside the Button action closure

💡 Hint

Think about where properties live in a struct.

@State variables must be declared as properties of the View struct, outside the body property. Declaring inside body or closures is invalid.

📝 Syntax

advanced

What error does this code produce?

What error will this SwiftUI code cause?

iOS Swift

struct ContentView: View {
  @State var name: String
  var body: some View {
    Text("Hello, \(name)!")
  }
}

A No error, code runs fine

B Cannot use @State with String type

C Missing body property error

D Property 'name' must have an initial value or be optional

💡 Hint

Check how @State variables must be initialized.

@State variables must have an initial value because SwiftUI manages their storage. Declaring without initialization causes a compile error.

🔧 Debug

advanced

Why does the UI not update?

Given this code, why does the Text not update when the button is tapped?

iOS Swift

struct ContentView: View {
  var count = 0
  var body: some View {
    VStack {
      Text("Count: \(count)")
      Button("Tap") {
        count += 1
      }
    }
  }
}

A Because the Button action is empty and does not change count

B Because the Text view is outside the VStack

C Because 'count' is not marked with @State, so changes don't trigger UI updates

D Because 'count' is a constant and cannot be changed

💡 Hint

Think about what triggers SwiftUI to refresh the view.

Without @State, changing 'count' does not notify SwiftUI to update the UI. The variable is just a normal property and changes are ignored for UI refresh.

🧠 Conceptual

expert

What is the role of @State in SwiftUI?

Which statement best describes the purpose of the @State property wrapper in SwiftUI?

A @State stores mutable data owned by a view and triggers UI updates when changed

B @State is used to declare constants that never change

C @State shares data between multiple views without copying

D @State manages network requests asynchronously

💡 Hint

Consider how SwiftUI knows when to redraw a view.

@State marks data that belongs to a view and can change over time. When the data changes, SwiftUI automatically refreshes the view to reflect the new state.

Practice

1. What is the main purpose of the @State property wrapper in SwiftUI?

easy

A. To keep track of data that can change and update the UI automatically

B. To create a constant value that never changes

C. To store data permanently on the device

D. To define a function inside a view

Solution

1. Step 1: Understand @State role

   @State is used to hold data that can change inside a SwiftUI view.

2. Step 2: Connect data change to UI update

   When @State data changes, SwiftUI automatically refreshes the view to show the new data.

3. Final Answer:

   To keep track of data that can change and update the UI automatically -> Option A

4. Quick Check:

   @State updates UI on data change = B [OK]

Hint: Remember: @State means data changes update the screen [OK]

Common Mistakes:

• Thinking @State stores permanent data
• Confusing @State with constants
• Using @State for functions

2. Which of the following is the correct way to declare a @State variable for an integer counter in SwiftUI?

easy

A. @State let counter: Int = 0

B. var @State counter: Int = 0

C. private var @State counter = 0

D. @State private var counter = 0

Solution

1. Step 1: Check correct @State syntax

   The correct syntax places @State before the variable declaration and usually uses private for encapsulation.

2. Step 2: Identify valid declaration

   @State private var counter = 0 uses '@State private var counter = 0' which is the recommended and correct form.

3. Final Answer:

   @State private var counter = 0 -> Option D

4. Quick Check:

   @State before var, private optional = D [OK]

Hint: Always put @State before 'var' and use private if needed [OK]

Common Mistakes:

• Placing @State after var
• Missing var keyword
• Using let instead of var

3. Consider this SwiftUI code snippet:

struct ContentView: View {
  @State private var count = 0
  var body: some View {
    VStack {
      Text("Count: \(count)")
      Button("Add") {
        count += 1
      }
    }
  }
}

What happens when the "Add" button is tapped?

medium

A. The app crashes because count is private

B. The count increases but the Text does not update

C. The count increases by 1 and the Text updates to show the new count

D. Nothing happens because @State variables cannot change

Solution

1. Step 1: Understand @State behavior on change

   When the button increments count, the @State variable changes.

2. Step 2: UI updates automatically

   SwiftUI detects the change and refreshes the Text to show the new count value.

3. Final Answer:

   The count increases by 1 and the Text updates to show the new count -> Option C

4. Quick Check:

   @State change triggers UI update = C [OK]

Hint: @State changes always refresh the UI automatically [OK]

Common Mistakes:

• Thinking private stops UI updates
• Assuming UI won't refresh on state change
• Believing @State variables are immutable

4. What is wrong with this SwiftUI code?

struct ContentView: View {
  @State var text: String
  var body: some View {
    TextField("Enter text", text: $text)
  }
}

medium

A. TextField cannot bind to @State variables

B. @State variables must have an initial value

C. The body property must return a Button, not TextField

D. @State cannot be used inside a struct

Solution

1. Step 1: Check @State variable declaration

   @State variables must be initialized with a value when declared.

2. Step 2: Identify missing initial value

   Here, 'text' has no initial value, causing a compile error.

3. Final Answer:

   @State variables must have an initial value -> Option B

4. Quick Check:

   @State needs initial value = A [OK]

Hint: Always give @State variables a starting value [OK]

Common Mistakes:

• Forgetting to initialize @State variables
• Thinking @State can't bind to TextField
• Confusing struct rules with @State usage

5. You want to create a toggle switch that changes a text label between "On" and "Off" using @State. Which code snippet correctly implements this behavior?

hard

A. struct ContentView: View {
@State private var isOn = false
var body: some View {
VStack {
Toggle("Switch", isOn: $isOn)
Text(isOn ? "On" : "Off")
}
}
}

B. struct ContentView: View {
var isOn = false
var body: some View {
VStack {
Toggle("Switch", isOn: $isOn)
Text(isOn ? "On" : "Off")
}
}
}

C. struct ContentView: View {
@State var isOn: Bool
var body: some View {
VStack {
Toggle("Switch", isOn: $isOn)
Text(isOn ? "On" : "Off")
}
}
}

D. struct ContentView: View {
@State private var isOn = false
var body: some View {
VStack {
Toggle("Switch", isOn: isOn)
Text(isOn ? "On" : "Off")
}
}
}

Solution

1. Step 1: Check @State declaration and initialization

   struct ContentView: View { @State private var isOn = false var body: some View { VStack { Toggle("Switch", isOn: $isOn) Text(isOn ? "On" : "Off") } } } correctly declares @State private var isOn = false, initializing the state.

2. Step 2: Verify Toggle binding

   The Toggle uses $isOn to bind to the state variable, enabling UI updates on toggle.

3. Step 3: Confirm Text updates with state

   The Text view uses a ternary to show "On" or "Off" based on isOn value.

4. Final Answer:

   code correctly implements the toggle and text update -> Option A

5. Quick Check:

   @State with $ binding updates UI = A [OK]

Hint: Use @State with $ for binding Toggle to update UI [OK]

Common Mistakes:

• Not initializing @State variable
• Missing $ for binding in Toggle
• Declaring @State without initial value