Missing method in AppDelegate for tracking push "opened" metrics

[sheeroo]

User Story

As a customer I want to know if I have properly configured the SDK so that I can better troubleshoot any issues.

Acceptance Criteria:

• Running the tool in an iOS native project will call out any issues based on the latest version of the SDK.
• Running the tool in an RN native project will call out any issues based on the latest version of the RN SDK.
• Running the tool in an RN native project will call out any issues based on the latest version of the RN SDK.

Technical notes:

Today, the self-service tool will scan an AppDelegate file and look for source code that indicates that a customer has followed all of the SDK integration steps required for opened push metrics. If the tool does not find this source code in the AppDelegate, then the tool throws an error in the output.

Since iOS version 2.11, the automatic push click handling feature is available that no longer requires the code that the self-service tool looks for in the AppDelegate.

Acceptance criteria

• self-service tool no longer throws an error to user, if their AppDelegate does not contain opened metrics code, previously required before 2.11

Scope?

There are a few different ways that this issue can be resolved.

• Check for MessagingPushAPN.initialize or MessagingPushFCM.initialize in the AppDelegate instead?
• Check if customer on latest iOS SDK version and if not, suggest they upgrade so they get at least 2.11.
• If the self-service tool finds this old code required < 2.11 in AppDelegate, do we point customers to the iOS SDK upgrade documentation to upgrade to 2.11?

[levibostian]

Thanks for bringing up this issue @sheeroo. Sorry to cause you confusion by this error.

This error that you have received on your app and our included sample app was caused by the recent 2.11 release in the native iOS SDK. As you can see in our upgrade docs, code that the doctor tool is checking in the AppDelegate for is no longer required 🎊!

We are aware of this error message and are in the process of updating the tool to fix that. Unfortunately I am not able to provide a release date for this fix.

In the mean time, I suggest following our latest push setup docs and do not be concerned about this particular error message from the doctor tool.

Thanks again for sending us this question!