Build configurations (Debug, Release) in iOS Swift - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to print a message only in Debug mode.

iOS Swift

#if [1]
  print("This is Debug mode")
#endif

Drag options to blanks, or click blank then click option'

APRODUCTION

BTESTING

CRELEASE

DDEBUG

Attempts:

3 left

💡 Hint

Common Mistakes

Using RELEASE instead of DEBUG causes the code to run only in Release builds.

Forgetting the #if directive syntax.

In Swift, the DEBUG flag is set for Debug builds, so checking #if DEBUG allows code to run only in Debug mode.

2fill in blank

medium

Complete the code to print a message only in Release mode.

iOS Swift

#if [1]
print("This is Release mode")
#endif

Drag options to blanks, or click blank then click option'

A!DEBUG

BDEBUG

CRELEASE

DPRODUCTION

Attempts:

3 left

💡 Hint

Common Mistakes

Using RELEASE directly is not a default flag in Swift builds.

Forgetting the #if and #endif directives.

The condition #if !DEBUG means the code runs when DEBUG is not set, which is typically the Release build.

3fill in blank

hard

Fix the error in the code to print a debug message only in Debug builds.

iOS Swift

#if [1]
print("Debug build active")
#endif

Drag options to blanks, or click blank then click option'

ADEBUG

BRELEASE

CTEST

DPROD

Attempts:

3 left

💡 Hint

Common Mistakes

Using RELEASE or other undefined flags causes the code not to compile or run as expected.

The correct flag to check for Debug builds is DEBUG, not RELEASE or other names.

4fill in blank

hard

Fill both blanks to define a variable only in Debug mode and assign it a value.

iOS Swift

#if [1]
let mode = [2]
#endif

Drag options to blanks, or click blank then click option'

ADEBUG

B"Debug"

C"Release"

DRELEASE

Attempts:

3 left

💡 Hint

Common Mistakes

Assigning the string "Release" inside the Debug block.

Using RELEASE flag instead of DEBUG.

The variable should be defined only in Debug mode using #if DEBUG and assigned the string "Debug".

5fill in blank

hard

Fill all three blanks to print different messages for Debug and Release modes.

iOS Swift

#if [1]
print([2])
#else
print([3])
#endif

Drag options to blanks, or click blank then click option'

ADEBUG

B"Debug mode active"

C"Release mode active"

DRELEASE

Attempts:

3 left

💡 Hint

Common Mistakes

Using RELEASE flag which is not predefined.

Mixing up the print messages.

Use #if DEBUG to check Debug mode, print "Debug mode active" there, else print "Release mode active".

Practice

1. What is the main purpose of having separate Debug and Release build configurations in an iOS app?

easy

A. To change the app's icon automatically

B. To switch programming languages

C. To create different versions of the app for testing and for users

D. To disable all app features

Solution

1. Step 1: Understand build configurations

   Debug and Release configurations allow different settings for testing and final app versions.

2. Step 2: Identify the purpose

   Debug is for testing with extra info; Release is optimized for users without debug info.

3. Final Answer:

   To create different versions of the app for testing and for users -> Option C

4. Quick Check:

   Build configurations = different app versions [OK]

Hint: Debug = testing, Release = user version [OK]

Common Mistakes:

• Thinking build configs change app icons automatically
• Confusing build configs with programming languages
• Believing build configs disable features

2. Which Swift code snippet correctly runs only in Debug build configuration?

easy

A. #if DEBUG
print("Debug mode")
#endif

B. if DEBUG { print("Debug mode") }

C. if #DEBUG { print("Debug mode") }

D. debug { print("Debug mode") }

Solution

1. Step 1: Recall Swift conditional compilation syntax

   Swift uses #if ... #endif for build config checks.

2. Step 2: Identify correct syntax

   Only #if DEBUG print("Debug mode") #endif uses #if DEBUG and #endif correctly.

3. Final Answer:

   #if DEBUG print("Debug mode") #endif -> Option A

4. Quick Check:

   #if DEBUG ... #endif = correct syntax [OK]

Hint: Use #if DEBUG ... #endif for build checks [OK]

Common Mistakes:

• Using if DEBUG without #if and #endif
• Writing #DEBUG instead of #if DEBUG
• Using unknown keywords like debug

3. Given this Swift code snippet, what will print when running a Release build?

#if DEBUG
print("Debug build")
#else
print("Release build")
#endif

medium

A. Compile error

B. Debug build

C. Nothing prints

D. Release build

Solution

1. Step 1: Understand conditional compilation

   #if DEBUG runs only in Debug builds; #else runs otherwise.

2. Step 2: Identify build type

   In Release build, DEBUG is not defined, so #else block runs.

3. Final Answer:

   Release build -> Option D

4. Quick Check:

   Release build prints "Release build" [OK]

Hint: Release build runs #else block in #if DEBUG [OK]

Common Mistakes:

• Assuming Debug print runs in Release
• Thinking nothing prints in Release
• Expecting compile error from #if

4. You wrote this code but it causes a compile error:

if #DEBUG {
  print("Debug mode")
}

What is the error and how to fix it?

medium

A. Use #if DEBUG ... #endif instead of if #DEBUG

B. Replace #DEBUG with DEBUG without #

C. Add parentheses after #DEBUG

D. Change if to switch

Solution

1. Step 1: Identify incorrect syntax

   Swift uses #if ... #endif for build config checks, not if #DEBUG.

2. Step 2: Correct syntax usage

   Replace if #DEBUG with #if DEBUG ... #endif block.

3. Final Answer:

   Use #if DEBUG ... #endif instead of if #DEBUG -> Option A

4. Quick Check:

   Use #if DEBUG ... #endif for build checks [OK]

Hint: Use #if ... #endif, not if #DEBUG [OK]

Common Mistakes:

• Using if #DEBUG instead of #if DEBUG
• Adding parentheses after #DEBUG
• Trying to use switch for build configs

5. You want to log detailed info only in Debug builds but avoid any logging in Release builds. Which approach is best in Swift?

hard

A. Use Release build for testing logs

B. Wrap logging code inside #if DEBUG ... #endif blocks

C. Always log and filter logs manually later

D. Use runtime checks like if isDebugMode { ... } without build flags

Solution

1. Step 1: Understand build-time code inclusion

   #if DEBUG ... #endif includes code only in Debug builds, excluding it from Release.

2. Step 2: Compare alternatives

   Runtime checks still include code in Release, wasting resources; logging always wastes resources; Release build is for users, not testing.

3. Final Answer:

   Wrap logging code inside #if DEBUG ... #endif blocks -> Option B

4. Quick Check:

   #if DEBUG excludes code from Release [OK]

Hint: Use #if DEBUG to exclude debug code from Release [OK]

Common Mistakes:

• Using runtime flags that don't remove code in Release
• Logging always and filtering later wastes resources
• Using Release build for testing logs