我的应用显示空白地图 [英] my app is showing blank map
本文介绍了我的应用显示空白地图的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我在我的应用程序中使用google map api.该地图运行正常，但现在它一片空白.Map仍在工作，但未加载地图.我正在搜索答案几个小时，但未得到任何结果.在Google云端平台上创建了一个新的api，并放置了该api，但仍未加载地图. 任何可以帮助我的人.谢谢！
I am using google map api in my app.The map was working perfectly but now it get blanked.Map is still working but not loading the map.I was searching answer for hours but didn't get any results.I have created a new api at google cloud platform and put that api but still not loading the map. Anyone who can help me with this. Thanks!
这是空白地图的屏幕截图. 地图的屏幕截图
Here is the screenshot of blank map. Screenshot of map
07-21 21:28:59.573 18146-18265/com.example.har.firebaseauthenticationdemo E/Google Maps Android API: Authorization failure. Please see https://developers.google.com/maps/documentation/android-api/start for how to correctly set up the map.
07-21 21:28:59.575 18146-18265/com.example.har.firebaseauthenticationdemo E/Google Maps Android API: In the Google Developer Console (https://console.developers.google.com)
Ensure that the "Google Maps Android API v2" is enabled.
Ensure that the following Android Key exists:
API Key: AIzaSyDWCP4m0DF57jZU4V8Yr7RFP2-DmhpgL34
Android Application (<cert_fingerprint>;<package_name>): 0E:0E:68:77:05:BB:76:A3:5C:BC:62:F8:6A:AB:A5:5F:2A:7F:37:5F;com.example.har.firebaseauthenticationdemo
07-21 21:29:00.571 2256-2451/? E/Auth: [GoogleAccountDataServiceImpl] getToken() -> BAD_AUTHENTICATION. Account: <ELLIDED:-895295850>, App: com.google.android.gms, Service: oauth2:https://www.googleapis.com/auth/login_manager
fkq: Long live credential not available.
at fkr.b(:com.google.android.gms@12529024@12.5.29 (040700-192802242):20)
at fkr.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):50)
at fjb.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):35)
at gzf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):8)
at gzf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):160)
at gyf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):2)
at gyc.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):17)
at gyc.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):6)
at cug.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):25)
at cug.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):79)
at cug.onTransact(:com.google.android.gms@12529024@12.5.29 (040700-192802242):8)
at android.os.Binder.transact(Binder.java:627)
at cwl.onTransact(:com.google.android.gms@12529024@12.5.29 (040700-192802242):3)
at android.os.Binder.execTransact(Binder.java:697)
07-21 21:29:00.611 2256-3646/? E/Auth: [GoogleAccountDataServiceImpl] getToken() -> BAD_AUTHENTICATION. Account: <ELLIDED:-895295850>, App: com.google.android.gms, Service: oauth2:https://www.googleapis.com/auth/login_manager
fkq: Long live credential not available.
at fkr.b(:com.google.android.gms@12529024@12.5.29 (040700-192802242):20)
at fkr.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):50)
at fjb.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):35)
at gzf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):8)
at gzf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):160)
at gyf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):2)
at gyc.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):17)
at gyc.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):6)
at cug.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):25)
at cug.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):79)
at cug.onTransact(:com.google.android.gms@12529024@12.5.29 (040700-192802242):8)
at android.os.Binder.transact(Binder.java:627)
at cwl.onTransact(:com.google.android.gms@12529024@12.5.29 (040700-192802242):3)
at android.os.Binder.execTransact(Binder.java:697)
07-21 21:29:00.673 2256-3646/? E/Auth: [GoogleAccountDataServiceImpl] getToken() -> BAD_AUTHENTICATION. Account: <ELLIDED:-895295850>, App: com.google.android.gms, Service: oauth2:https://www.googleapis.com/auth/login_manager
fkq: Long live credential not available.
at fkr.b(:com.google.android.gms@12529024@12.5.29 (040700-192802242):20)
at fkr.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):50)
at fjb.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):35)
at gzf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):8)
at gzf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):160)
at gyf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):2)
at gyc.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):17)
at gyc.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):6)
at cug.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):25)
at cug.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):79)
at cug.onTransact(:com.google.android.gms@12529024@12.5.29 (040700-192802242):8)
at android.os.Binder.transact(Binder.java:627)
at cwl.onTransact(:com.google.android.gms@12529024@12.5.29 (040700-192802242):3)
at android.os.Binder.execTransact(Binder.java:697)
07-21 21:29:00.748 2426-18282/? E/ChromeSync: [Sync,SyncAdapter] Failed to sync.
mbz: fgj: BadAuthentication
at mfy.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):5)
at mgm.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):42)
at mgn.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):22)
at mgn.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):73)
at mgn.b(:com.google.android.gms@12529024@12.5.29 (040700-192802242):7)
at mgl.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):41)
at nrg.onPerformSync(:com.google.android.gms@12529024@12.5.29 (040700-192802242):5)
at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:321)
Caused by: fgj: BadAuthentication
at ffx.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):13)
at ffw.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):2)
at ffw.e(:com.google.android.gms@12529024@12.5.29 (040700-192802242):6)
at ffw.d(:com.google.android.gms@12529024@12.5.29 (040700-192802242):1)
at ffu.b(:com.google.android.gms@12529024@12.5.29 (040700-192802242):1)
at nms.b(Unknown Source:6)
at nlf.b(:com.google.android.gms@12529024@12.5.29 (040700-192802242):5)
at nlw.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):58)
at mfy.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):1)
at mgm.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):42)
at mgn.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):22)
at mgn.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):73)
at mgn.b(:com.google.android.gms@12529024@12.5.29 (040700-192802242):7)
at mgl.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):41)
at nrg.onPerformSync(:com.google.android.gms@12529024@12.5.29 (040700-192802242):5)
at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:321)
07-21 21:29:03.389 1599-1612/? E/memtrack: Couldn't load memtrack module
07-21 21:29:05.559 1599-1612/? E/memtrack: Couldn't load memtrack module
07-21 21:29:05.574 1599-1612/? E/memtrack: Couldn't load memtrack module
07-21 21:29:12.866 2256-18310/? E/Auth: [GoogleAccountDataServiceImpl] getToken() -> BAD_AUTHENTICATION. Account: <ELLIDED:-895295850>, App: com.google.android.gms, Service: oauth2:https://www.googleapis.com/auth/experimentsandconfigs
fkq: Long live credential not available.
at fkr.b(:com.google.android.gms@12529024@12.5.29 (040700-192802242):20)
at fkr.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):50)
at fjb.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):35)
at gzf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):8)
at gzf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):160)
at gyf.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):2)
at gyc.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):17)
at gyc.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):6)
at cug.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):25)
at cug.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):79)
at ffx.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):6)
at ffw.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):2)
at ffw.e(:com.google.android.gms@12529024@12.5.29 (040700-192802242):6)
at ffu.f(:com.google.android.gms@12529024@12.5.29 (040700-192802242):3)
at ffu.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):4)
at ffu.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):7)
at aenk.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):22)
at aenm.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):130)
at aenm.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):243)
at aenm.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):404)
at com.google.android.gms.phenotype.sync.HeterodyneSyncTaskChimeraService.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):66)
at com.google.android.gms.phenotype.sync.HeterodyneSyncTaskChimeraService.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):20)
at ulu.run(:com.google.android.gms@12529024@12.5.29 (040700-192802242):1)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)
07-21 21:29:12.884 2256-18310/? E/HeterodyneSyncTaskChime: Failed to get auth token: User intervention required. Notification has been pushed. -- metadata{ service_id: 51 }
fgk: User intervention required. Notification has been pushed.
at ffu.f(:com.google.android.gms@12529024@12.5.29 (040700-192802242):10)
at ffu.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):4)
at ffu.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):7)
at aenk.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):22)
at aenm.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):130)
at aenm.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):243)
at aenm.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):404)
at com.google.android.gms.phenotype.sync.HeterodyneSyncTaskChimeraService.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):66)
at com.google.android.gms.phenotype.sync.HeterodyneSyncTaskChimeraService.a(:com.google.android.gms@12529024@12.5.29 (040700-192802242):20)
at ulu.run(:com.google.android.gms@12529024@12.5.29 (040700-192802242):1)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)
推荐答案
确保已启用"Google Maps Android API v2".
Ensure that the "Google Maps Android API v2" is enabled.
- 转到 Google控制台 API，然后搜索适用于Android API的地图.并确保已启用.
- Go to Google Console APIs and search for Maps for android API. and ensure it's enabled.
- 转到Google控制台凭据管理器.并添加用于调试和发布的Android API密钥.查看 Google文档以获取更多详细信息.
- Go to Google Console Credential Manager. and add android API key for debug and release. Check Google Doc for more details.
- 从您的logcat中获取.
确保存在以下Android密钥:
Ensure that the following Android Key exists:
更新1
07-21 21:28:59.573 18146-18265/com.example.har.firebaseauthenticationdemo E/Google地图 Android API:授权失败.
07-21 21:28:59.573 18146-18265/com.example.har.firebaseauthenticationdemo E/Google Maps Android API: Authorization failure.
请参阅 https://developers.google.com/maps/documentation/android-api/start 了解如何正确设置地图.
Please see https://developers.google.com/maps/documentation/android-api/start for how to correctly set up the map.
更新2
build.gradle
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
resValue "string", "google_maps_api_key", "Release_API_KEY"
}
debug {
// KL MBP debug Key
resValue "string", "google_maps_api_key", "DEBUG_API_KEY"
// KL Old Machine debug Key
// resValue "string", "google_maps_api_key", "DEBUG_API_KEY"
}
}
AndroidManifest.xml
<meta-data
android:name="com.google.android.maps.v2.API_KEY"
android:value="@string/google_maps_api_key"/>
<uses-library
android:name="com.google.android.maps"
android:required="true" />
更新3
获取SHA1以用于生成API密钥
- 对于Linux或macOS，打开终端窗口并输入以下内容:
macOS和Linux:
~/.android/
keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
- 对于Windows Vista和Windows 7，运行:
Windows Vista和Windows 7:
Windows Vista and Windows 7:
C:\Users\your_user_name\.android\ List the SHA-1 fingerprint:
keytool -list -v -keystore "%USERPROFILE%\.android\debug.keystore" -alias androiddebugkey -storepass android -keypass android
更新4
在Android Studio中，您可以找到所有应用程序签名信息，而无需任何控制台命令:
In Android Studio you can find all your app signing information without any console command:
- 打开您的项目
- 在右侧面板上单击Gradle
- 在Gradle项目面板中打开文件夹:您的项目->任务-> Android
- 运行signingReport任务(双击)，您将在Gradle控制台中看到结果(密钥库路径，SHA1，MD5等).
这篇关于我的应用显示空白地图的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
