> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Avoid Common Push Notification Issues on iOS Devices Using iOS Swift version 7.x.x?

> Fix push impression tracking and image rendering on iOS with Swift SDK 7.x.x. Check appgroupid configuration in your MoEngage project settings.

## Problem

Common issues with Push notifications, including Push Campaign impressions not being tracked and images not rendering even though Push notifications are successfully delivered to device with Swift version 7.x.x.

<Info>
  For Push Campaign impressions to be tracked, verify that the **Show iOS impressions** toggle on the MoEngage dashboard is turned on.

  <img src="https://mintcdn.com/moengage/T-dEj4C-7pywzBS3/images/moengage_a3edc2.png?fit=max&auto=format&n=T-dEj4C-7pywzBS3&q=85&s=bc3cc82b6d292d041851753f65793971" alt="iOS imp.png" width="2744" height="1582" data-path="images/moengage_a3edc2.png" />
</Info>

## Solution

Perform the following steps:

1. **Check for app\_group\_id in your project’s main target for each configuration**:
   You can add the same app\_group\_id or different ones across configurations.
   <Info>
     If your configurations use different Bundle Identifiers but share the same app\_group\_id, issues may arise. Specifically, if two apps with different Bundle Identifiers but the same app\_group\_id are installed on the same device, the Notification Service Extension may fail.
     To avoid this, you can use the same app\_group\_id across multiple configurations, but be aware that you won't be able to test all apps simultaneously on a single device.
   </Info>
   <img src="https://mintcdn.com/moengage/S5VM4C7aiU6sct6c/images/moengage_053674.png?fit=max&auto=format&n=S5VM4C7aiU6sct6c&q=85&s=9ff176b82bdf0f2cf750597f5e1cb4ca" alt="app group.png" width="1920" height="709" data-path="images/moengage_053674.png" />
2. **Check for app\_group\_id during SDK initialization**:
   * If the SDK is initialized using info.plist, the APP\_GROUP\_ID key must be there inside the MoEngage key in your info.plist file.
   * If the SDK is initialized using sdkConfig, the APP\_GROUP\_ID must be in the sdkConfig variable inside the AppDelegate file.\
     **app\_group\_id in info.plist:**
     <img src="https://mintcdn.com/moengage/prFQLkdcYp4xSt9t/images/moengage_667e35.png?fit=max&auto=format&n=prFQLkdcYp4xSt9t&q=85&s=bf6324154507b577d72be8e630926192" alt="app id.png" width="1920" height="888" data-path="images/moengage_667e35.png" />
     **app\_group\_id in sdkConfig variable:**
   ```swift Swift theme={null}
   var sdkConfig = MOSDKConfig.init(appID: "XXXXXXXXXXXXXXXX")
   sdkConfig.moeDataCenter = DATA\_CENTER\_0X
   sdkConfig.appGroupID = "group.com.XXXXXXXXXXXXXXXX"
   //if SDK initialized without sdkConfig in AppDelegate file
   MoEngage.setAppGroupID("group.com.moengage.MIPL567.demo")
   ```
   ```Objective-C Objective-C theme={null}
   MOSDKConfig\* sdkConfig = [[MOSDKConfig alloc] initWithAppID: @"XXXXXXXXXXXXXXXX"];
   sdkConfig.moeDataCenter = DATA\_CENTER\_0X;
   sdkConfig.appGroupID = @"group.com.XXXXXXXXXXXXXXXX";
   //if SDK initialized without sdkConfig in AppDelegate file
   [MoEngage setAppGroupID: @"group.com.XXXXXXXXXXXXXXXX"];
   ```
3. **Check for a Notification Service Extension Target**:
   * **Enable Push Notifications**: In the extension target's Signing & Capabilities section, make sure to enable Push Notifications and add the AppGroupId.
     <img src="https://mintcdn.com/moengage/8EX_gHAg3q4zA1kw/images/moengage_23f29a.png?fit=max&auto=format&n=8EX_gHAg3q4zA1kw&q=85&s=45c8cd1f8f353d3e001d74018a76af09" alt="enable.png" width="1920" height="706" data-path="images/moengage_23f29a.png" />
   * **Align the Minimum Deployment iOS Version**: Ensure that the minimum deployment iOS version of the Notification Service Extension matches the iOS version of the main app.
     <img src="https://mintcdn.com/moengage/-X0av6ek9AEOUtsy/images/moengage_cb3695.png?fit=max&auto=format&n=-X0av6ek9AEOUtsy&q=85&s=8cde3e02fc5ab39f803ef3da413d8e2b" alt="support.png" width="1920" height="563" data-path="images/moengage_cb3695.png" />
4. Integrate the MORichNotification Framework into the Notification Service Extension target.
   ```swift Swift theme={null}
   target 'MoEngageDemo' do
     use_frameworks!
     pod 'MoEngage-iOS-SDK'
   end
   target 'MoEngageNotificationService' do
     use_frameworks! #use use_frameworks only if included in main target as in above scenario
     pod 'MORichNotification'
   end
   ```
5. NotificationService.swift file looks like this:
   ```swift Swift theme={null}
   import UserNotifications
   import MORichNotification
    
   class NotificationService: UNNotificationServiceExtension {
    
       var contentHandler: ((UNNotificationContent) - Void)?
       var bestAttemptContent: UNMutableNotificationContent?
    
       override func didReceive(_ request: UNNotificationRequest, withContentHandler contentHandler: @escaping (UNNotificationContent) - Void) {	
         MORichNotification.setAppGroupID("group.com.XXXXXXXXXXXXXXXX")
         self.contentHandler = contentHandler
         bestAttemptContent = (request.content.mutableCopy() as? UNMutableNotificationContent)
         MORichNotification.handle(request, withContentHandler: contentHandler)
       }
       
       override func serviceExtensionTimeWillExpire() {
           // Called just before the extension will be terminated by the system.
           // Use this as an opportunity to deliver your "best attempt" at modified content, otherwise the original push payload will be used.
           if let contentHandler = contentHandler, let bestAttemptContent =  bestAttemptContent {
               contentHandler(bestAttemptContent)
           }
       }
   }
   ```
6. **Check Build Phases for the Main App Target**: In the Build Phases section of the main app target, locate the Embed App Extensions / Embed Foundation Extensions section. Ensure that the **Copy only when installing** option is unchecked.

<img src="https://mintcdn.com/moengage/xaH8HoR16_YVDek5/images/moengage_cfdd8e.png?fit=max&auto=format&n=xaH8HoR16_YVDek5&q=85&s=de18a2fe829e17cc0cb6484074d584fc" alt="copy.png" width="1920" height="652" data-path="images/moengage_cfdd8e.png" />

7. **Ensure Consistent appGroupId Across Configurations**: Verify that the appGroupId is consistent across all schemes and configurations (e.g. Debug/Release/QA/UAT) in the project.
8. **Align Build Configuration**: When running or archiving the project, ensure that the Build Configuration for the Main Target and Notification Service Extension Target points to the same scheme/configuration.

<img src="https://mintcdn.com/moengage/o0kXRAcOq2mxzDnY/images/moengage_ef15c5.png?fit=max&auto=format&n=o0kXRAcOq2mxzDnY&q=85&s=11ade9afaae65618cf3532aa5e8b50a4" alt="run.png" width="1750" height="556" data-path="images/moengage_ef15c5.png" />

<img src="https://mintcdn.com/moengage/H6NVBgn3z5fYOOBq/images/moengage_7a3664.png?fit=max&auto=format&n=H6NVBgn3z5fYOOBq&q=85&s=473f6f90a29e22202599ec72bfe9763b" alt="build.png" width="1832" height="446" data-path="images/moengage_7a3664.png" />
