ILICENSE and PT_SUBSCRIPTION | developer.brewmp.com ILICENSE and PT_SUBSCRIPTION | developer.brewmp.com

Developer

ILICENSE and PT_SUBSCRIPTION

Forums:

Hi all!
I have a simple question about using ILICENSE:

Let's say I used ILICENSE_GetPurchaseInfo(...) and got PT_SUBSCRIPTION as return code. Does the argument LicenseType return any valid information (LT_USES, LT_DATE etc) as PT_PURCHASE does?

What will I get in case the subscriber cancels the app subscription after the first month? What will the return code be for a ILICENSE_GetPurchaseInfo(...) call in such case? Does it change MIF information and send the cancelation to the BDS?

Thanks,

Rodrigo Corbera.

:( Well, it sounds like nobody knows an answer for my first question. I'll make it simpler then:
- An APP running as PT_SUBSCRIPTION will cause the billing system at the Operator to bill the subscriber every month.
How does the APP know when the subscriber cancels the subscription?
Is that billing system informed about it?
Please could anyone answer that question?
Thanks in advance,

:( Well, it sounds like nobody knows an answer for my first question. I'll make it simpler then:
- An APP running as PT_SUBSCRIPTION will cause the billing system at the Operator to bill the subscriber every month.
How does the APP know when the subscriber cancels the subscription?
Is that billing system informed about it?
Please could anyone answer that question?
Thanks in advance,

I think if you are using the "subscription" type license, the application will not start if the user has cancelled the subscription. (you dont need to handle it, brew does automatically)
-Tyndal

I think if you are using the "subscription" type license, the application will not start if the user has cancelled the subscription. (you dont need to handle it, brew does automatically)
-Tyndal

But I'm still a bit confused... :D
If the APP will handle it, it means the program I'm developing will handle it, right?
I've understood from your message, for example, that my APP will check if it's PT_SUBSCRIPTION or PT_PURCHASE + LT_NONE and then execute itself.
In case the subscriber cancels the subscription BREW will delete the APP from his/her phone. And in case of unlimited use there is no problem at all.
Is that what you said?
Tnxs,

But I'm still a bit confused... :D
If the APP will handle it, it means the program I'm developing will handle it, right?
I've understood from your message, for example, that my APP will check if it's PT_SUBSCRIPTION or PT_PURCHASE + LT_NONE and then execute itself.
In case the subscriber cancels the subscription BREW will delete the APP from his/her phone. And in case of unlimited use there is no problem at all.
Is that what you said?
Tnxs,

The only case that your app is required to deal with involves LT_USES. BREW does not define a "use" and so your app must be programmed to handle that case. All other cases are handled by BREW and your app only needs to be aware of them if you wish for it to behave differently.
For example, if you just want to make sure that your app will not run if a user has cancelled his subscription, you need not do anything because BREW handles this case. BREW does not delete your app from the phone, it simply will not allow the app to be run. That way the user could renew the subscription and begin using the app again without having to re-download it.
However, if you want your app to behave differently if it is a subscription than if it is a purchase, then you will have to write code to implement the difference.

The only case that your app is required to deal with involves LT_USES. BREW does not define a "use" and so your app must be programmed to handle that case. All other cases are handled by BREW and your app only needs to be aware of them if you wish for it to behave differently.
For example, if you just want to make sure that your app will not run if a user has cancelled his subscription, you need not do anything because BREW handles this case. BREW does not delete your app from the phone, it simply will not allow the app to be run. That way the user could renew the subscription and begin using the app again without having to re-download it.
However, if you want your app to behave differently if it is a subscription than if it is a purchase, then you will have to write code to implement the difference.