首页
学习
活动
专区
圈层
工具
发布
首页
学习
活动
专区
圈层
工具
MCP广场
社区首页 >问答首页 >如何解决Android中的表型API错误?

如何解决Android中的表型API错误?
EN

Stack Overflow用户
提问于 2020-08-21 19:18:36
回答 1查看 4.9K关注 0票数 8

我正在使用Java在Android中构建一个简单的空间入侵者游戏。我以前在比赛中没有看到这些错误。Android文件夹中的项目和其他项目运行良好,但是我可能意外地碰到了错误,所有的项目在运行程序时都会出现类似的错误。我使用的是带有API 29的模拟器,我安装的SDK平台是API 29,API 30。我试过的是:

  • 擦除数据,使用不同的模拟器。
  • 确保包名在清单中是相同的
  • 卸载,然后重新安装平台工具\

我使用的资料来源:未能打开QEMU管道'qemud:network':无效参数 [https://www.thetopsites.net/article/53766789.shtml\](https://www.thetopsites.net/article/53766789.shtml%5C) [22629568\](https://stackoverflow.com/questions/22629568/couldnt-load-memtrack-module-logcat-error/22745487#comment34571006_22629568%5C) 使用Android“无法找到亚行”

我安装的SDK工具\

逻辑猫:

代码语言:javascript
运行
复制
2020-08-21 12:03:33.345 2100-2136/system_process E/system_server: Invalid ID 0x00000000.
2020-08-21 12:03:33.539 10844-10844/? E/e.spaceinvader: Unknown bits set in runtime_flags: 0x8000
2020-08-21 12:03:33.825 1839-1996/? E/SurfaceFlinger: ro.sf.lcd_density must be defined as a build property
2020-08-21 12:03:37.954 1948-1948/? E/wifi_forwarder: RemoteConnection failed to initialize: RemoteConnection failed to open pipe
2020-08-21 12:03:38.015 1946-1946/? E/netmgr: Failed to open QEMU pipe 'qemud:network': Invalid argument
2020-08-21 12:03:44.406 2100-2140/system_process E/memtrack: Couldn't load memtrack module
2020-08-21 12:03:55.561 2339-3855/com.google.android.gms.persistent E/amvj: Phenotype API error. Event # byvc@1a946355, EventCode: 12 [CONTEXT service_id=51 ]
    amum: 29503
        at amvp.b(:com.google.android.gms@200414022@20.04.14 (040700-294335909):27)
        at amvj.a(:com.google.android.gms@200414022@20.04.14 (040700-294335909):91)
        at amvj.a(:com.google.android.gms@200414022@20.04.14 (040700-294335909):77)
        at aabf.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):7)
        at bkdt.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):2)
        at srw.b(:com.google.android.gms@200414022@20.04.14 (040700-294335909):14)
        at srw.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):2)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at sxw.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):0)
        at java.lang.Thread.run(Thread.java:919)
2020-08-21 12:03:55.561 2339-3855/com.google.android.gms.persistent E/AsyncOperation: serviceID=51, operation=GetCommittedConfigurationOperationCall
    OperationException[Status{statusCode=unknown status code: 29503, resolution=null}]
        at amvj.a(:com.google.android.gms@200414022@20.04.14 (040700-294335909):92)
        at amvj.a(:com.google.android.gms@200414022@20.04.14 (040700-294335909):77)
        at aabf.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):7)
        at bkdt.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):2)
        at srw.b(:com.google.android.gms@200414022@20.04.14 (040700-294335909):14)
        at srw.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):2)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at sxw.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):0)
        at java.lang.Thread.run(Thread.java:919)
2020-08-21 12:03:55.562 2339-4663/com.google.android.gms.persistent E/NetRec: [147] ajzf.a: Could not retrieve server token for package com.google.android.apps.gcs
    java.util.concurrent.ExecutionException: rmz: 29503: 
        at atjq.b(:com.google.android.gms@200414022@20.04.14 (040700-294335909):5)
        at atjq.a(:com.google.android.gms@200414022@20.04.14 (040700-294335909):23)
        at ajzf.a(:com.google.android.gms@200414022@20.04.14 (040700-294335909):1)
        at ajzf.a(:com.google.android.gms@200414022@20.04.14 (040700-294335909):4)
        at ajze.getHeaders(:com.google.android.gms@200414022@20.04.14 (040700-294335909):2)
        at com.android.volley.toolbox.HttpClientStack.performRequest(:com.google.android.gms@200414022@20.04.14 (040700-294335909):20)
        at sle.performRequest(:com.google.android.gms@200414022@20.04.14 (040700-294335909):1)
        at bme.executeRequest(:com.google.android.gms@200414022@20.04.14 (040700-294335909):1)
        at com.android.volley.toolbox.BasicNetwork.performRequest(:com.google.android.gms@200414022@20.04.14 (040700-294335909):10)
        at slf.performRequest(:com.google.android.gms@200414022@20.04.14 (040700-294335909):17)
        at com.android.volley.NetworkDispatcher.a(:com.google.android.gms@200414022@20.04.14 (040700-294335909):6)
        at com.android.volley.NetworkDispatcher.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):2)
     Caused by: rmz: 29503: 
        at rsm.a(:com.google.android.gms@200414022@20.04.14 (040700-294335909):4)
        at amux.b(:com.google.android.gms@200414022@20.04.14 (040700-294335909):3)
        at amvp.a(:com.google.android.gms@200414022@20.04.14 (040700-294335909):7)
        at aabf.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):15)
        at bkdt.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):2)
        at srw.b(:com.google.android.gms@200414022@20.04.14 (040700-294335909):14)
        at srw.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):2)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at sxw.run(:com.google.android.gms@200414022@20.04.14 (040700-294335909):0)
        at java.lang.Thread.run(Thread.java:919)
2020-08-21 12:03:55.626 2339-4663/com.google.android.gms.persistent E/Volley: [147] BasicNetwork.performRequest: Unexpected response code 400 for https://mobilenetworkscoring-pa.googleapis.com/v1/GetWifiQuality?key=AIzaSyBrlVtd67QvwS_Wz0Do4ZIdOeA6ThtVczU

2020-08-21 12:05:53.238 2339-2339/com.google.android.gms.persistent E/BeaconBle: Missing BluetoothAdapter
2020-08-21 12:05:53.247 2339-2339/com.google.android.gms.persistent E/BeaconBle: Scan couldn't start for Places
EN

Stack Overflow用户

发布于 2021-05-23 23:13:00

对我来说,这是由布局文件中遗漏的错误造成的。我错误地从一个layout_width中删除了EditText属性,当我试图构建它时,我得到了Phenotype API错误。

票数 0
EN
查看全部 1 条回答
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/63528897

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档