【问题标题】:Play games services not working after upgrading to gms services 8.1升级到 gms 服务 8.1 后玩游戏服务无法正常工作
【发布时间】:2015-12-31 13:05:33
【问题描述】:

我有一个使用玩游戏服务多年的现有 Android 应用程序 (https://play.google.com/store/apps/details?id=fr.pixelprose.dice)...自 6 月下旬以来我没有升级它,排行榜、登录等运行良好...

上周我尝试将播放服务从 7.x 升级到 8.1,并按照此处描述的步骤获取分析配置文件:https://developers.google.com/analytics/devguides/collection/android/v4/

从那时起,没有人可以在我的应用程序中登录,使用已发布的版本和我得到的正在开发的版本:

03 13:25:18.815 9741-27255/? E/SignInIntentService: There is no linked app associated with this client ID.
10-03 13:25:18.815 9741-27255/? E/SignInIntentService: com.google.android.gms.games.server.error.GamesException
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at com.google.android.gms.games.server.GamesServer.getResponseBlocking(GamesServer.java:164)
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at com.google.android.gms.games.broker.PlayerAgent.getPlayerFromNetwork(PlayerAgent.java:1700)
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at com.google.android.gms.games.broker.PlayerAgent.fetchPlayer(PlayerAgent.java:621)
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at com.google.android.gms.games.broker.DataBroker.loadSelf(DataBroker.java:920)
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at com.google.android.gms.games.service.PlayGamesSignInIntentService$LoadSelfOperation.executeInternal(PlayGamesSignInIntentService.java:402)
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at com.google.android.gms.games.service.PlayGamesSignInIntentService$BaseOperation.execute(PlayGamesSignInIntentService.java:51)
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at com.google.android.gms.games.service.PlayGamesSignInIntentService$OperationAdapter.execute(PlayGamesSignInIntentService.java:487)
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at com.google.android.gms.chimera.BaseAsyncOperationService$OperationTask.run(BaseAsyncOperationService.java:179)
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
10-03 13:25:18.815 9741-27255/? E/SignInIntentService:     at java.lang.Thread.run(Thread.java:818)
10-03 13:25:18.826 25900-25900/? E/LoadSelfFragment: Unable to sign in - application does not have a registered client ID

但是:

我怎样才能摆脱在这里设置分析引入的错误配置:https://developers.google.com/mobile/add ???

【问题讨论】:

    标签: android google-plus google-play-games google-signin


    【解决方案1】:

    对于那些想知道如何解决此问题的人,您必须在 play 开发者控制台中再次关联您的应用程序...(就像您设置了一个新的关联应用程序:https://developers.google.com/games/services/console/enabling

    所以我现在有两次与游戏服务关联的同一个应用程序......两者都具有相同的 app_id 但不完全是:

    • {app_id}.apps.googleusercontent.com旧的不再工作了
    • {app_id}-{other_id}.apps.googleusercontent.com 新的运行良好

    【讨论】:

    • 你能澄清一下 other_id 是什么吗?
    • 非常感谢。在过去的两天里,我一直在为此苦苦挣扎。你刚刚挽救了我的理智!
    • 天哪,即使认为它行不通,我也尝试过......它成功了!非常感谢,伙计!
    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 2013-11-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2014-12-18
    • 2018-10-05
    • 1970-01-01
    相关资源
    最近更新 更多