Do we need two Launch properties for integrating ACS push notifications in AEP SDK mobile applicaiton?

[rupaljain2408]

Hi All, 

Last year, I was working on ACS push notifications (Collect PII) using Adobe launch and our mobile application integrated with AEP SDK. We found a limitation that we need to create two different Launch properties for two environments - staging and production, since ACS has unique certificates for each environment. Even though there are 3 end points shown in settings in Launch property. Also, there is only one to one mapping in ACS with Launch property. 

I wanted to know if this limitation still exist? Or can we just have one Launch property for both environments with two separate certificate keys?

Attaching screenshot here.

Thank you in advance,

Rupal Jain

[archanac3012 · Accepted solution]

In ACS Mobile SDK,  the 3 URLs for dev, stage and production were available with the assumption that for customers wanting to test their pre-production workflows  they  will use different ACS instances. 

For different ACS instances it was possible to have an app credential in each instance to connect to the same Launch property.

eg:

1. ACS_stage_end_point + ACS_mobile_app (with pre-production push credential) 

2. ACS_prod_end_point + ACS_mobile_app (with production push credential)

Both  these URLs could be configured in the same Launch property.

Looks like in  your use-case the same ACS instance is used for both pre-production and production mobile app push credentials. This case will require you to create two mobile apps in ACS and two Launch properties to be connected to these mobile apps.