LVL Check timed out

[GoogleCodeExporter]

I recently begun receiving several emails every day saying that the license 
can't be verified. I haven't changed anything in my apps for over a month and 
this used to work just fine.
What seems to solve the problem is to uninstall and reinstall the app from the 
market. It started happening soon after the change from Android Market to 
Google Play so I don;t know if it's related but this looks kind of a strange 
coincidence.

The logs I receive from users have the following errors:
Line 925: 03-26 23:04:41.463 I/LicenseChecker(31875): Binding to licensing 
service.
Line 926: 03-26 23:04:41.473 I/LicenseChecker(31875): Calling checkLicense on 
service for com.blabla.myApp
Line 927: 03-26 23:04:41.473 I/LicenseChecker(31875): Start monitoring timeout.
Line 930: 03-26 23:04:51.472 I/LicenseChecker(31875): Check timed out.

I verified with all the users that had this problem that they had solid 
internet connection, and in my app I only fail the license check if it returns 
"don't allow" over 20 times, so this can't be something momentary that happened 
just once (and again, this used to work for almost a year and I haven't changed 
anything in my app over a month).

Original issue reported on code.google.com by Yaron.Muzikant on 12 Apr 2012 at 4:49

[GoogleCodeExporter]

I'm seeing the same behavior.

The default timeout in the market licensing library is 10s, which I increased 
to 100s for testing, but it still times out.

One thing I noticed is that the license check passes on a stock 2.2 phone, but 
times out on a CyanogenMod phone. I haven't asked the users that reported this 
if they're running a custom ROM, but maybe there's a connection. Yaron - can 
you comment on that?

Original comment by dbschu...@gmail.com on 13 May 2012 at 2:06

[GoogleCodeExporter]

One thing that made a difference was to upgrade the Google Play store to 
version 3.5.19. After the update, I immediately received a LICENSED response.

Original comment by dbschu...@gmail.com on 13 May 2012 at 2:29

[GoogleCodeExporter]

It seems to be a problem with the local Google play install. What cleared it up 
for me was to clear the app data for google play. Before, all lvl requests kept 
timing out. After clearing, lvl functionality was as expected. 

Original comment by calvert....@gmail.com on 13 May 2012 at 2:33

[GoogleCodeExporter]

Before i saw this, i filed a defect report. It happened on the droid 3 to only 
one of the apps I have.  how do we upgrade ( install) to a different version of 
the google play?  what is meant by clearing app data for google play.

Original comment by swtest.b...@gmail.com on 17 May 2012 at 1:12

[GoogleCodeExporter]

I have just had this issue too & can confirm that deleting the Google Play 
Application data (Settings, Applications, choose Google Play & press Clear Data 
) did fix it.  Clearing Cache is not sufficient.  Ihe only impact I saw of 
doing this (apart from my App now working again) is that you have to re-accept 
Google Play T&C etc when you next use that app and my search history had gone.  
I can't tell if this was issue caused by an update of Google Play or some other 
random event. Anyone have any ideas? This is a really nasty issue as it is 
likely to make the end user think that the main App is at fault which will 
probably gernerate unjustified negative market feedback.

Original comment by rcn...@googlemail.com on 1 Jun 2012 at 1:25

[GoogleCodeExporter]

I started a thread on xda 
(http://forum.xda-developers.com/showthread.php?t=1566770) for the same issue 
and so far the best solution I could find is to uninstall your app and 
reinstall it.
It probably has the same effect as clearing the market data but it's limited to 
your application and does not require the user to take extreme measures such as 
uninstalling the Google Play app (which I believe not all users will be willing 
to do)

Original comment by android....@gmail.com on 1 Jun 2012 at 1:31

[GoogleCodeExporter]

Uninstalling/reinstalling the App in my case did not make any difference. I 
even did an (already planned) system upgrade to ICS and the problem persisted 
over that too. I am not saying that you need to uninstall Google Play (I think, 
in most phones, you will not be able to do this anyway.) Just delete the data 
and force Google Play  to rebuild whatever is currently wrong.
The phone that had the problem was a Development one runnning the Market code 
but not downloaded from the Market - Perhaps that is why the 
uninstall/re-install didn't work?

Original comment by rcn...@googlemail.com on 1 Jun 2012 at 1:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thank you so much for that solution. I was banging my head on this for two days 
now. I thought I had the LVL setup wrong since its the first time I am using it 
and couldn't connect properly. I cleaned Google play data and now it is working 
perfectly.

Original comment by ort...@gmail.com on 2 Jul 2012 at 7:52

[GoogleCodeExporter]

We are observing this issue also. The last case was reported by user who 
performed factory reset of the device. In all cases that we had clearing data 
for Google Play Store helped. For sure this is increasing number of refunds.

Original comment by n7mob...@gmail.com on 3 Jul 2012 at 1:53

[GoogleCodeExporter]

I confirm that clearing data for Google Play Store resolves problem. But what 
to do with refunds and negative feedback? Fix it ASAP, please.

Original comment by ivan.chu...@gmail.com on 5 Jul 2012 at 2:57

[GoogleCodeExporter]

Btw got this problem on last Google Play Store ver. 3.5.19

Original comment by ivan.chu...@gmail.com on 5 Jul 2012 at 3:02

[GoogleCodeExporter]

I'm observing this issue also. Clearing Googlt Play data on the device solved 
the problem. Why is Google Play not warning anyone about this in their 
developer console at the very least?

Original comment by wytzesch...@gmail.com on 25 Jul 2012 at 2:13

[GoogleCodeExporter]

This is getting very annoying. every time I upgrade my app, the following 
several days/weeks I get emails about this issue. I'm seriously thinking of 
giving up this thing and consider alternative solutions. Any ideas ?

Original comment by android....@gmail.com on 25 Jul 2012 at 2:15

[GoogleCodeExporter]

@android...@gmail.com (comment #14)

My app displays instructions how to clean up data and the button that opens 
Google Play Store app properties page.

Original comment by ivan.chu...@gmail.com on 25 Jul 2012 at 6:55

[GoogleCodeExporter]

I've been seeing this also. It seems to mostly hit users who have more than one 
google account on their device. Maybe the wrong account is being checked with 
the market?

Original comment by w...@igoweb.org on 30 Jul 2012 at 11:50

[GoogleCodeExporter]

*PUSH*
Google, you need to fix this problem as soon as possible. It's getting 
annoying. My customers are very angry.

Original comment by omer.guv...@gmail.com on 4 Sep 2012 at 12:52

[GoogleCodeExporter]

Suddenly the license checking server doesn't respond anymore to one of the my 
published apps, causing timeout error.

Seems that the only way to get a successful checking is to rename my the app's 
package. Investigate to this bug and try to fix it as soon as possible, the LVL 
actually is unusable, too many bugs that cause serious problems to the users.

Original comment by maranosi...@gmail.com on 30 Oct 2012 at 4:21

[GoogleCodeExporter]

This bug isn't fixed yet. *PUSH*
The priority should be set to urgent/high.

Original comment by omer.guv...@gmail.com on 18 Jun 2013 at 6:49

[GoogleCodeExporter]

Agreed, I have someone email me with this issue every few weeks (and their data 
connection is usually fine.) It's very frustrating to not be able to do 
anything about this.

Original comment by tman...@gmail.com on 14 Jul 2013 at 9:36

[GoogleCodeExporter]

It seems the pre-compiled AIDL files are having wrong package name. After I did 
the following, the issue is gone. No data clearing required. (I'm using Android 
Studio/Gradle build, with sdk/extras/google/play_licensing Rev.2)

cd <path_to_lvl>/library
rm src/com/google/android/vending/licensing/ILicenseResultListener.java
rm src/com/google/android/vending/licensing/ILicensingService.java
mkdir -p aidl/com/android/vending/licensing
mv aidl/*.aidl aidl/com/android/vending/licensing/

[<path_to_lvl>/library/build.gradle]
...
android {
    ...
    sourceSets {
        main {
            manifest.srcFile 'AndroidManifest.xml'
            java.srcDirs = ['src']
            resources.srcDirs = ['src']
            // use the 'aidl' directory
            aidl.srcDirs = ['aidl']
            renderscript.srcDirs = ['src']
            res.srcDirs = ['res']
            assets.srcDirs = ['assets']
        }
    }
    ...
}
...

[<path_to_lvl>/library/src/com/google/android/vending/licensing/LicenseChecker.j
ava]
package com.google.android.vending.licensing;
// import the interfaces from the correct package
import com.android.vending.licensing.ILicenseResultListener;
import com.android.vending.licensing.ILicensingService;

PS: As of writing, https://code.google.com/p/android/issues/detail?id=60033 
still happens quite often with Java 1.7

Original comment by Ladios.J...@gmail.com on 2 Dec 2013 at 3:22