Push notifications (APNs + FCM) in iOS Swift - UI Render Trace

Component - Push notifications (APNs + FCM)

This UI component handles push notifications using Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM). It registers the device for notifications, requests user permission, and displays alerts when notifications arrive.

Widget Tree

AppDelegate
└── UIWindow
    └── RootViewController
        ├── UILabel (Status)
        └── UIButton (Request Permission)

The AppDelegate manages the app lifecycle and push notification registration. The UIWindow holds the RootViewController, which shows a label displaying notification status and a button to request notification permission from the user.

Render Trace - 4 Steps

Step 1: AppDelegate

Step 2: RootViewController

Step 3: UIButton (Request Permission)

Step 4: UNUserNotificationCenter Delegate

State Change - Re-render

Trigger:User taps 'Request Permission' button

Before

UILabel shows 'Notifications Disabled', no permission granted

→

After

UILabel updates to 'Notifications Enabled' if user allows notifications

Re-renders:RootViewController's UILabel updates to reflect new permission status

UI Quiz - 3 Questions

What happens when the user taps the 'Request Permission' button?

A The app immediately starts receiving notifications

B The system shows a dialog asking to allow notifications

C The app closes and reopens

D Nothing happens

Key Insight

Push notification setup requires coordinating app lifecycle (AppDelegate), user permission (UNUserNotificationCenter), and UI feedback (labels/buttons). Keeping UI updated with permission status helps users understand notification availability.

Practice

1. What is the primary purpose of APNs in iOS push notifications?

easy

A. To store app data locally

B. To manage user authentication

C. To deliver push notifications to iOS devices

D. To create user interface elements

Solution

1. Step 1: Understand APNs role

   APNs stands for Apple Push Notification service and is designed to send notifications to iOS devices.

2. Step 2: Differentiate from other services

   It does not handle authentication, data storage, or UI creation, only notification delivery.

3. Final Answer:

   To deliver push notifications to iOS devices -> Option C

4. Quick Check:

   APNs = notification delivery [OK]

Hint: APNs is Apple's service for sending notifications [OK]

Common Mistakes:

• Confusing APNs with authentication services
• Thinking APNs manages app data
• Assuming APNs creates UI elements

2. Which Swift code snippet correctly requests permission for push notifications?

easy

A. UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .sound]) { granted, error in }

B. UNUserNotificationCenter.requestAuthorization(options: [.alert])

C. UNNotificationCenter.current().requestPermission()

D. UserNotificationCenter.requestAuthorization(options: [.badge])

Solution

1. Step 1: Identify correct class and method

   The correct class is UNUserNotificationCenter and the method is requestAuthorization with options and completion handler.

2. Step 2: Check syntax correctness

   UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .sound]) { granted, error in } uses the correct syntax with options array and closure parameters.

3. Final Answer:

   UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .sound]) { granted, error in } -> Option A

4. Quick Check:

   Correct class and method = UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .sound]) { granted, error in } [OK]

Hint: Use UNUserNotificationCenter.current().requestAuthorization with options [OK]

Common Mistakes:

• Using wrong class names like UNNotificationCenter
• Omitting the completion handler closure
• Incorrect method names like requestPermission

3. Given this Swift code snippet, what will be printed if the device token is successfully received?

func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
    let tokenParts = deviceToken.map { data in String(format: "%02.2hhx", data) }
    let token = tokenParts.joined()
    print("Device Token: \(token)")
}

medium

A. Device Token: nil

B. Device Token:

C. Device Token: deviceToken

D. Device Token: [data]

Solution

1. Step 1: Understand deviceToken processing

   The deviceToken is converted byte-by-byte to a hexadecimal string representation.

2. Step 2: Analyze print output

   The print statement outputs "Device Token: " followed by the joined hex string, not the raw data or nil.

3. Final Answer:

   Device Token: <hexadecimal string> -> Option B

4. Quick Check:

   Device token converted to hex string = Device Token: <hexadecimal string> [OK]

Hint: Device token is hex string printed, not raw data [OK]

Common Mistakes:

• Expecting raw Data object printed
• Assuming deviceToken is nil
• Printing deviceToken without conversion

4. Identify the error in this Swift code snippet for registering remote notifications:

func registerForPushNotifications() {
    UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .badge, .sound]) { granted, error in
        if granted {
            DispatchQueue.main.async {
                UIApplication.shared.registerForRemoteNotifications()
            }
        }
    }
}

medium

A. Incorrect options array syntax

B. Missing call to UNUserNotificationCenter.current().delegate assignment

C. registerForRemoteNotifications() should be called outside DispatchQueue.main.async

D. No error, code is correct

Solution

1. Step 1: Verify permission request syntax

   UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .badge, .sound]) { granted, error in ... } uses correct class, method, options, and completion handler.

2. Step 2: Confirm registration call

   DispatchQueue.main.async ensures UIApplication.shared.registerForRemoteNotifications() runs on the main thread, which is correct practice.

3. Final Answer:

   No error, code is correct -> Option D

4. Quick Check:

   Standard registration flow followed correctly [OK]

Hint: This code correctly requests permission and registers for remote notifications [OK]

Common Mistakes:

• Thinking UNUserNotificationCenter delegate is required inside this registration function
• Claiming incorrect options array syntax
• Believing registerForRemoteNotifications should avoid DispatchQueue.main.async

5. You want to send a push notification to an iOS app using Firebase Cloud Messaging (FCM). Which step is essential to link APNs with FCM for this to work correctly?

hard

A. Upload the APNs authentication key or certificates to the Firebase Console

B. Enable Background Modes in Xcode without any APNs setup

C. Register the device token only with APNs, ignoring FCM

D. Use only APNs without configuring Firebase

Solution

1. Step 1: Understand FCM and APNs integration

   FCM requires APNs credentials to send notifications to iOS devices through Apple's service.

2. Step 2: Identify required configuration

   You must upload the APNs authentication key or certificates to Firebase Console to enable this link.

3. Final Answer:

   Upload the APNs authentication key or certificates to the Firebase Console -> Option A

4. Quick Check:

   APNs key upload to Firebase = Upload the APNs authentication key or certificates to the Firebase Console [OK]

Hint: Upload APNs key to Firebase to enable iOS push via FCM [OK]

Common Mistakes:

• Skipping APNs key upload to Firebase
• Relying only on Background Modes without APNs
• Ignoring FCM device token registration