Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

New AEM Mobile Cordova APIs for Subscriptions and Purchasing

Avatar

Level 2

Has anyone had any luck using the new AEM Mobile specific Cordova API for Subscriptions and Purchasing?

https://helpx.adobe.com/digital-publishing-solution/help/whats-new.html

We have rebuilt an app since the release/update and have tried to access subscription information via the API with no luck. We are able to access the Entitlement API and return data.

We have looked at the API docs however it is not clear as to how the subscription data should be called.

AEM Mobile specific Cordova-enabled plug-ins

Is there a new javascript file we should be including in our HTML?

Also what is the way we should request the information.

For example device information is

cq.mobile.device

and context information is

cq.mobile.context

1 Accepted Solution

Avatar

Correct answer by
Level 2

We have been able to get the information we needed.  It needs to be called similar to some of the entitlement methods.

cq.mobile.entitlement.getSubscriptionInfo(successHandler, failureHandler);

If successful it will return JSON data with information related to the subscriptions that are available. What we were missing was understanding that it was part of entitlement and not something else.

What would really have saved us time is if it could be a UX call like how you can call the signin box.

cq.mobile.user.launchSignInUX();

If something could be created that would call the subscribe UX it would work in about 90% of the time. 

View solution in original post

3 Replies

Avatar

Employee

I'll ask around. In the meantime, you might want to contact Adobe Support using the numbers listed when you sign in to the Portal using a master admin account.

Avatar

Level 2

Thank you Bob. I did just get an answer back from support. If that works I will post the solution here.

Avatar

Correct answer by
Level 2

We have been able to get the information we needed.  It needs to be called similar to some of the entitlement methods.

cq.mobile.entitlement.getSubscriptionInfo(successHandler, failureHandler);

If successful it will return JSON data with information related to the subscriptions that are available. What we were missing was understanding that it was part of entitlement and not something else.

What would really have saved us time is if it could be a UX call like how you can call the signin box.

cq.mobile.user.launchSignInUX();

If something could be created that would call the subscribe UX it would work in about 90% of the time.