> ## Documentation Index
> Fetch the complete documentation index at: https://moengage-user-guide.mintlify.site/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 Objective C version 8.x.x?

## 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 Objective C version 8.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-user-guide/w89gcvhxT1w_pzZQ/images/moengage_458274.png?fit=max&auto=format&n=w89gcvhxT1w_pzZQ&q=85&s=96bc2d5cf79f6bfd728ecde5a47a5b4c" alt="iOS imp.png" width="2744" height="1582" data-path="images/moengage_458274.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>
     Issues may arise if your configurations use different Bundle Identifiers but share the same app\_group\_id. Specifically, the Notification Service Extension may fail if two apps with different Bundle Identifiers but the same app\_group\_id are installed on the same device. 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-user-guide/1xZo5l7vwEi6w1Pv/images/moengage_d35dec.png?fit=max&auto=format&n=1xZo5l7vwEi6w1Pv&q=85&s=7f4b8c618649e58d588bbc94ac184b30" alt="app group.png" width="1920" height="709" data-path="images/moengage_d35dec.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-user-guide/-3vSwXDB0-23wJct/images/moengage_b4b13a.png?fit=max&auto=format&n=-3vSwXDB0-23wJct&q=85&s=4d85b5cafc6947ff43d25af0923ee99f" alt="app id.png" width="1920" height="888" data-path="images/moengage_b4b13a.png" />
     **app\_group\_id in sdkConfig variable:**
   <CodeGroup>
     ```objective-c Objective-C wrap theme={null}
     MOSDKConfig\* sdkConfig = [[MOSDKConfig alloc] initWithAppID: @"XXXXXXXXXXXXXXXX"];
     sdkConfig.moeDataCenter = MODataCenterData\_center\_0X;
     sdkConfig.appGroupID = @"group.com.XXXXXXXXXXXXXXXX";
     ```
   </CodeGroup>
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-user-guide/g8xpO9-GNN0zkyOa/images/moengage_82ff4d.png?fit=max&auto=format&n=g8xpO9-GNN0zkyOa&q=85&s=84d744a9f1ffd249bd5e56a6a32c57cd" alt="enable.png" width="1920" height="706" data-path="images/moengage_82ff4d.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 alt="support.png" src="https://mintcdn.com/moengage-user-guide/f9utDwqBcydYgMUJ/images/moengage_431d64.png?fit=max&auto=format&n=f9utDwqBcydYgMUJ&q=85&s=24e9a3996fed5b2714dbc666b1c45411" width="1920" height="563" data-path="images/moengage_431d64.png" />
4. Integrate the MORichNotification framework into the Notification Service Extension target.
   ```objective-c Objective-C 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 'MoEngageRichNotification'
   end
   ```
5. NotificationService.m file looks like this:
   ```objective-c Objective-C theme={null}
   #import "NotificationService.h"
   #import 
   @interface NotificationService ()
    
   @property (nonatomic, strong) void (^contentHandler)(UNNotificationContent *contentToDeliver);
   @property (nonatomic, strong) UNMutableNotificationContent *bestAttemptContent;
    
   @end
    
   @implementation NotificationService
    
   - (void)didReceiveNotificationRequest:(UNNotificationRequest *)request withContentHandler:(void (^)(UNNotificationContent * _Nonnull))contentHandler {
       @try {
         	[MORichNotification setAppGroupID: @"group.com.XXXXXXXXXXXXXXXX"];
           self.contentHandler = contentHandler;
           self.bestAttemptContent = [request.content mutableCopy];
           [MORichNotification handleWithRichNotificationRequest:request withContentHandler:contentHandler];
       } @catch (NSException *exception) {
           NSLog(@"MoEngage : exception : %@",exception);
       }
   }
    
   /// Save the image to disk
   - (void)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.
       self.contentHandler(self.bestAttemptContent);
   }
   @end
   ```
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-user-guide/g5z_bz8PEWXqJHJ6/images/moengage_9bb544.png?fit=max&auto=format&n=g5z_bz8PEWXqJHJ6&q=85&s=f8400b924ba833a6a059f7ac56ab227a" alt="copy.png" width="1920" height="652" data-path="images/moengage_9bb544.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-user-guide/2PfbfD5dSGY7Pno5/images/moengage_569a68.png?fit=max&auto=format&n=2PfbfD5dSGY7Pno5&q=85&s=d362aa123918cb8df5f74d7cd740425b" alt="run.png" width="1750" height="556" data-path="images/moengage_569a68.png" />
   <img src="https://mintcdn.com/moengage-user-guide/zi8OFpJJZ8wcpIWO/images/moengage_29f224.png?fit=max&auto=format&n=zi8OFpJJZ8wcpIWO&q=85&s=2005fe022ba5348c1d08d3af429b7fad" alt="build.png" width="1832" height="446" data-path="images/moengage_29f224.png" />
