Google Maps Android API no coincide entre cliente y paquete
08-04 22:51:16.947 4393 4393 I Google Maps Android API: Google Play services client version: 9452000 08-04 22:51:16.951 4393 4393 I Google Maps Android API: Google Play services package version: 9452480
Esta es la versión que tengo, cada vez que se actualizan, lucho por alguna razón para que funcione de nuevo, google maps (react-native-maps) no quiere cargar.
compileSdkVersion 23 buildToolsVersion "23.0.1" compile 'com.google.android.gms:play-services-maps:9.4.0'
He actualizado los servicios de reproducción de Google en el Administrador de SDK. He estado tratando de usar un '+'
lugar, sigue siendo el mismo error. Intenté 9.4.52 , pero no puede encontrarlo cuando compile la aplicación
- Google Map Api v2 muestra que la clase de descriptor de módulo local no se encuentra
- Versión de actualización de conflictos a play-services 9.4.0 Android studio 2.2
- Android google play juegos seleccionar actividad para iniciar cuando se hace clic en la notificación
- Android Google Places autocomplete los límites de la API que no funcionan
- Proyecto de API carece de ID de proyecto en Google Developers Console
Mi emulador está utilizando la revisión 32 de Google Play Services, con Android 23, revisión 16. Esto es lo que tengo en el teléfono: http://www.apkmirror.com/apk/google-inc/google-play-services/google-play -services-9-4-52-release / google-play-services-9-4-52-480-127739847-android-apk-download /
<meta-data android:name="com.google.android.gms.version" android:value="@integer/google_play_services_version" />
Aquí está el build.gradle
apply plugin: "com.android.application" import com.android.build.OutputFile /** * The react.gradle file registers a task for each build variant (eg bundleDebugJsAndAssets * and bundleReleaseJsAndAssets). * These basically call `react-native bundle` with the correct arguments during the Android build * cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the * bundle directly from the development server. Below you can see all the possible configurations * and their defaults. If you decide to add a configuration block, make sure to add it before the * `apply from: "../../node_modules/react-native/react.gradle"` line. * * project.ext.react = [ * // the name of the generated asset file containing your JS bundle * bundleAssetName: "index.android.bundle", * * // the entry file for bundle generation * entryFile: "index.android.js", * * // whether to bundle JS and assets in debug mode * bundleInDebug: false, * * // whether to bundle JS and assets in release mode * bundleInRelease: true, * * // whether to bundle JS and assets in another build variant (if configured). * // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants * // The configuration property can be in the following formats * // 'bundleIn${productFlavor}${buildType}' * // 'bundleIn${buildType}' * // bundleInFreeDebug: true, * // bundleInPaidRelease: true, * // bundleInBeta: true, * * // the root of your project, ie where "package.json" lives * root: "../../", * * // where to put the JS bundle asset in debug mode * jsBundleDirDebug: "$buildDir/intermediates/assets/debug", * * // where to put the JS bundle asset in release mode * jsBundleDirRelease: "$buildDir/intermediates/assets/release", * * // where to put drawable resources / React Native assets, eg the ones you use via * // require('./image.png')), in debug mode * resourcesDirDebug: "$buildDir/intermediates/res/merged/debug", * * // where to put drawable resources / React Native assets, eg the ones you use via * // require('./image.png')), in release mode * resourcesDirRelease: "$buildDir/intermediates/res/merged/release", * * // by default the gradle tasks are skipped if none of the JS files or assets change; this means * // that we don't look at files in android/ or ios/ to determine whether the tasks are up to * // date; if you have any other folders that you want to ignore for performance reasons (gradle * // indexes the entire tree), add them here. Alternatively, if you have JS files in android/ * // for example, you might want to remove it from here. * inputExcludes: ["android/**", "ios/**"] * ] */ apply from: "../../node_modules/react-native/react.gradle" /** * Set this to true to create two separate APKs instead of one: * - An APK that only works on ARM devices * - An APK that only works on x86 devices * The advantage is the size of the APK is reduced by about 4MB. * Upload all the APKs to the Play Store and people will download * the correct one based on the CPU architecture of their device. */ def enableSeparateBuildPerCPUArchitecture = false /** * Run Proguard to shrink the Java bytecode in release builds. */ def enableProguardInReleaseBuilds = false android { compileSdkVersion 23 buildToolsVersion "23.0.1" defaultConfig { applicationId "com.obv" minSdkVersion 16 targetSdkVersion 22 versionCode 1 versionName "1.0" ndk { abiFilters "armeabi-v7a", "x86" } } splits { abi { reset() enable enableSeparateBuildPerCPUArchitecture universalApk false // If true, also generate a universal APK include "armeabi-v7a", "x86" } } buildTypes { release { minifyEnabled enableProguardInReleaseBuilds proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro" } } // applicationVariants are eg debug, release applicationVariants.all { variant -> variant.outputs.each { output -> // For each separate APK per architecture, set a unique version code as described here: // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits def versionCodes = ["armeabi-v7a":1, "x86":2] def abi = output.getFilter(OutputFile.ABI) if (abi != null) { // null for the universal-debug, universal-release variants output.versionCodeOverride = versionCodes.get(abi) * 1048576 + defaultConfig.versionCode } } } packagingOptions { exclude 'META-INF/DEPENDENCIES.txt' exclude 'META-INF/LICENSE.txt' exclude 'META-INF/NOTICE.txt' exclude 'META-INF/NOTICE' exclude 'META-INF/LICENSE' exclude 'META-INF/DEPENDENCIES' exclude 'META-INF/notice.txt' exclude 'META-INF/license.txt' exclude 'META-INF/dependencies.txt' exclude 'META-INF/LGPL2.1' } } dependencies { compile fileTree(dir: "libs", include: ["*.jar"]) compile "com.android.support:appcompat-v7:23.0.1" compile "com.facebook.react:react-native:+" // From node_modules compile 'com.google.android.gms:play-services-maps:9.4.0' compile 'com.airbnb.android:react-native-maps:0.7.1' } // Run this once to be able to run the application with BUCK // puts all compile dependencies into folder libs for BUCK to use task copyDownloadableDepsToLibs(type: Copy) { from configurations.compile into 'libs' }
- GamesClient no se conecta. Error: "Llamar a connect () y esperar a que onConnected () sea llamado."
- API de reconocimiento de actividad no confiable?
- Después de la actualización de Google Play Service a la versión 13, recibí un error
- Servicios de juegos de Google Play en un juego de escritorio
- Play Servicios de ubicación getLastLocation devuelve null
- Cómo usar el reconocimiento de actividad para detectar caminar / correr vs on_foot
- Encontrado com.google.android.gms: play-services: 8.4.0, pero la versión 8.3.0 es necesaria para el plugin google-services
- Programaticamente abierto a la página de servicios de Google Play para mi aplicación
Pensé que había añadido todos los StyleSheet en el mapa, pero sólo me doy cuenta de que no lo hice. He añadido esto y funcionó:
container: { position: 'absolute', top: 0, left: 0, right: 0, bottom: 0, width: 400, justifyContent: 'flex-end', alignItems: 'center', }, map: { position: 'absolute', top: 0, left: 0, right: 0, bottom: 0, },
Aparentemente no tener la misma versión no importa?
- Cómo obtener datos de MySQL con dos fechas diferentes en android y mostrar en Multi Column ListView
- El teléfono Android se reinicia al desinstalar