Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better use of developer payload? #4

Open
paritosh-gupta opened this issue Aug 6, 2018 · 0 comments
Open

Better use of developer payload? #4

paritosh-gupta opened this issue Aug 6, 2018 · 0 comments

Comments

@paritosh-gupta
Copy link

paritosh-gupta commented Aug 6, 2018

Hi there,

Is there a reason why the developer payload is passed to the Security Manager as the base64 public key?

I would rather have another variable in the constructor and let the user put whatever developer payload he wants.

(dataSignature != null && SecurityManager.verifyPurchase(developerPayload, purchaseData, dataSignature))) {

fun verifyPurchase(base64PublicKey: String, signedData: String, signature: String): Boolean {

Thanks for the awesome library!!

@paritosh-gupta paritosh-gupta changed the title Misuse of developerpayload Better use of developer payload? Aug 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant