Welcome!

Welcome to the Official BlackBerry Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
inside custom component

BlackBerry® World™ Development

Reply
Developer
sblantipodi
Posts: 1,175
Registered: ‎02-19-2009

Dynamic licensing makes an HTTP POST with blank email field.

Hi all,

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?

Please use plain text.
Developer
pbrebs
Posts: 40
Registered: ‎09-08-2011
My Carrier: AIS

Re: Dynamic licensing makes an HTTP POST with blank email field.

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.

Please use plain text.
Developer
sblantipodi
Posts: 1,175
Registered: ‎02-19-2009

Re: Dynamic licensing makes an HTTP POST with blank email field.

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.

Please use plain text.
Developer
Developer
mb1
Posts: 306
Registered: ‎05-26-2009

Re: Dynamic licensing makes an HTTP POST with blank email field.

Does it happen for all apps or only Playbook apps?

Please use plain text.
Developer
sblantipodi
Posts: 1,175
Registered: ‎02-19-2009

Re: Dynamic licensing makes an HTTP POST with blank email field.

mmm... this is something that I don't know... How can I know from the HTTP Post if I sold a BlackBerry App or a PlayBook App?

Please use plain text.
Developer
Developer
mb1
Posts: 306
Registered: ‎05-26-2009

Re: Dynamic licensing makes an HTTP POST with blank email field.

We  consistently get this error for Playbook apps, never for Blackberry phone apps .

 

Please use plain text.
Developer
sblantipodi
Posts: 1,175
Registered: ‎02-19-2009

Re: Dynamic licensing makes an HTTP POST with blank email field.

how do you know if it is a playbook apps or a smartphone one from the HTTP Post?

Please use plain text.
Developer
Developer
mb1
Posts: 306
Registered: ‎05-26-2009

Re: Dynamic licensing makes an HTTP POST with blank email field.

Our PB apps are different from phone apps.


sblantipodi wrote:

how do you know if it is a playbook apps or a smartphone one from the HTTP Post?


 

Please use plain text.
Developer
sblantipodi
Posts: 1,175
Registered: ‎02-19-2009

Re: Dynamic licensing makes an HTTP POST with blank email field.

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?

Please use plain text.
Developer
sblantipodi
Posts: 1,175
Registered: ‎02-19-2009

Re: Dynamic licensing makes an HTTP POST with blank email field.

[ Edited ]

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:

0000000000134385697345

 

when I get the Device ID from the HTTP Post I get something like this:

134385697345

 

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?

So bad.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Please use plain text.