Google Android LVL CheckLicense服务超时 [英] Google Android LVL CheckLicense service timeout

查看:187
本文介绍了Google Android LVL CheckLicense服务超时的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个使用Google许可证保护服务的应用。我已经成功测试了该应用程序(已经有好几个星期了,目前已经在Google Play上进行了测试)以及许可证检查。



几天前,我发布了具有相同保护和另一个私有功能的另一个应用程序



静态最终字节[] SALT =新字节[] {....}



并且此应用程序的许可证检查也很好



今天,我已经更新了第一个发布的应用程序的布局。
我已经测试过该应用程序,但令我惊讶的是,许可证检查失败并出现超时问题(并且我的Internet连接正常)

  10-25 01:04:16.689:I / LicenseChecker(2739):绑定到许可服务。 
10-25 01:04:16.709:I / LicenseChecker(2739):在服务myapp.package.comu上调用checkLicense
10-25 01:04:16.709:I / LicenseChecker(2739):开始监视超时。
10-25 01:04:26.719:I / LicenseChecker(2739):检查超时。
10-25 01:04:28.579:I / LicenseChecker(2739):绑定到许可服务。
myapp.package.comu
10-25 01:04:28.609:I / LicenseChecker(2739):开始监视超时。
10-25 01:04:38.619:I / LicenseChecker(2739):检查超时。

我已经尝试从控制台更改许可证响应,但没有成功,许可证检查服务没有



在具有不同软件包和我发布的相同保护逻辑的第二个应用程序中,LVL可以正常工作。

strong>



我不知道可能是这个问题的原因。



我也尝试使用相同的 SALT 数组没有成功。



现在,我只能希望应用程序的购买者不会遇到同样的问题。



有什么想法吗?

解决方案

该错误已在Google许可中服务器或Google Play应用中由于某种奇怪的原因随机导致设置中的数据损坏并拒绝与该应用的连接。
如果您更改了程序包名称,则服务器会正​​确响应。



很明显,更改程序包名称很烦人,如果应用程序已经在市场上确实存在问题。 / p>

一种解决方法是



1)卸载应用程序



2)清除所有 Google Play商店应用数据不仅缓存 Google Play服务数据,在电话设置中。



3)重新打开Goog​​le Play并接受最终用户许可协议。



4)重新安装该应用。



我试图与Google联系以解决问题。


I have an app that use Google license protection service. I have tested successfully this app(that currently is on Google Play since a couple of weeks) and the license checking.

Some days ago I have published another app with the same protection and another private

static final byte[] SALT = new byte[] {....}

And the license checking works fine also with this app.

Today I have updated a single layout of the first app published. I have tested the app and with my surprise fails the license checking with a timeout problem (and my Internet connection works fine)

10-25 01:04:16.689: I/LicenseChecker(2739): Binding to licensing service.
10-25 01:04:16.709: I/LicenseChecker(2739): Calling checkLicense on service for myapp.package.comu
10-25 01:04:16.709: I/LicenseChecker(2739): Start monitoring timeout.
10-25 01:04:26.719: I/LicenseChecker(2739): Check timed out.
10-25 01:04:28.579: I/LicenseChecker(2739): Binding to licensing service.
myapp.package.comu
10-25 01:04:28.609: I/LicenseChecker(2739): Start monitoring timeout.
10-25 01:04:38.619: I/LicenseChecker(2739): Check timed out.

I have already tried to change my license response from the console without success, license checking service doesn't responds anything to my app.

In the second app with a different package and the same protection logic that I have published, LVL works without any problem.

I cannot figure what could be the reason of this issue.

I have tried also to use the same SALT array without success.

Now I can only hope that buyers of the app haven't the same issue.

Any idea?

解决方案

The bug is on the Google Licensing Server or in Google Play App that for some strange reason randomly causes a data corruption in the settings and refuse the connection to the App. If you change the package name the server responds right.

Obviously change the package name is annoying and if app was already on the market is really problematic.

A workaround is this:

1) Uninstall the app

2) Clean all Google Play Store App data not only the cache, and Google Play Service data, in the phone setting.

3) Reopen Google Play and accept the end-user license agreement.

4) Reinstall the app.

I have tried to contact Google to Solve the problem.

这篇关于Google Android LVL CheckLicense服务超时的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆