I have added email of my device in "Test accounts" and testing LVL by
setting values in Test response box in Developer Console.

Sometimes in LicenseValidator.verify(PublicKey publicKey, int
responseCode, String signedData, String signature) I get signedData ==
null and signature == null.

In Logcat I see:
10-13 01:41:03.758: ERROR/vending(4738):
com.android.vending.AsynchRequestRunner$1.runRequestRetryingFailure():
Got ApiException from async request: Got unexpected HTTP status code:
503

And sometimes I see "Check timed out" in logcat and application don't
allow me to use it. It is ResultListener.mOnTimeout runnable launched
by service. When I press Retry (i.e. call checkAccess(...) again)
several times (and sometimes - many times!) , it finally works (calls
allow()).

It seems that server sometimes is out of service. And not all
developers have implemented LVL calls in their apps for now. What will
be next - it will be continuosly out of service?

Currently we have tons of letters from customers keep saying "won't
download!!!". Yes, it's because of market server is out of service.
But of course we're to blame - from customer's point of view. So I
suppose once we add LVL in our apps we'll have tons of letters from
saying "won't let me to launch!!!" :) Am I right?

Google guys, can you please explane such problems with LVL? I just
can't decide - should I add LVL check or leave all things as is...

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to