05-27-2012 12:20 PM
all my apps use dynamic licensing using the App World HTTP Post to my server that replys with an activation code for the user who buy the software.
This HTTP Post from the app world to my server must contain the email address of the user who bought the software,
recently the http post is done correctly but it doesn't contain the email address of the user, why?
This is really boring for me, why I don't receive the email address of my customer from time to time?
05-27-2012 03:19 PM
Is the Transaction ID new? I expect not.
Perhaps the user has changed device - in which case the PIN would be different.
Or it could just be a lookup, with the same PIN.
05-27-2012 04:00 PM
yes the transactionid is NEW.
when the transaction ID isn't new, since years, the App World sent the same HTTP Post as the normal one, email included.
05-30-2012 04:14 PM
Our PB apps are different from phone apps.
how do you know if it is a playbook apps or a smartphone one from the HTTP Post?
06-04-2012 03:39 PM
the http post received from PlayBook is completely scrambled, the transaction id does not meet the receipt who received the customer, it does not contain the email of the customer and the device id is messed up.
what does it happening?
06-08-2012 08:30 AM - edited 06-08-2012 08:35 AM
Investigating the problem I founded something more...
The HTTP post generated from the Tablet devices lacks the email address, this is really boring,
specially when you think that the transaction id sent in the HTTP post does not meet the receipt ID that the customer have.
With all this problems you don't have any way to track if a user bought your software or not from your database.
The only way to see if the user bought the software is to see if the device id is present in the database but here there is another problem.
I noticed that the device id sent in the HTTP post is correct but it lacks the initial zeros.
When I check the device id from my app I get something like this:
when I get the Device ID from the HTTP Post I get something like this:
this obviously creates problem when generating the correct activation code because the strings are different.
Should I manually truncate the initial zeros when detecting the device id inside my apps before generating an activation code?