应用已发布但未在 Google 中编入索引 2 周后播放
App published but not indexed in Google Play after 2 weeks
我们为我们的客户创建了一个应用程序,该应用程序必须在 10 月 11 日之前可用。该应用程序已在 iOS 应用程序商店中可用,但 Google 播放似乎有问题。
我已将软件包添加到 9 月 26 日的发布轨道,希望它能在不久后得到审核和发布,幸运的是,它确实做到了。
我可以对应用程序(取自游戏控制台)使用 direct link,这表明它已正确发布。控制台没有列出任何错误。
设备和国家/地区设置已经过仔细检查,一切似乎都是正确的。
Google 几天前联系了支持,但不幸的是,他们仍然没有回复。
随着截止日期的临近,我每晚的睡眠越来越少。
有没有人对这个特定问题有任何经验并希望找到解决方案?
备注
- 应用是使用 React Native 版本 0.59.9 创建的
- 没有广告,但使用 AdMob SDK for Firebase Analytics
- 包名称是 "com.kunstmuseum.kunstmuseum"
- 在 Play 商店中搜索:"pub:Kunstmuseum Den Haag" 确实给了我一个结果。
AndroidManifest.xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.kunstmuseum.kunstmuseum"
android:versionCode="1"
android:versionName="1.0">
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<application
android:name=".MainApplication"
android:allowBackup="true"
android:label="@string/app_name"
android:icon="@mipmap/ic_launcher"
android:roundIcon="@mipmap/ic_launcher_round"
android:theme="@style/AppTheme">
<activity
android:name=".MainActivity"
android:label="@string/app_name"
android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
android:screenOrientation="portrait"
android:windowSoftInputMode="adjustResize">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
<service android:name="io.invertase.firebase.messaging.RNFirebaseMessagingService">
<intent-filter>
<action android:name="com.google.firebase.MESSAGING_EVENT" />
</intent-filter>
</service>
<service android:name="io.invertase.firebase.messaging.RNFirebaseInstanceIdService">
<intent-filter>
<action android:name="com.google.firebase.INSTANCE_ID_EVENT" />
</intent-filter>
</service>
</application>
build.gradle
apply plugin: "com.android.application"
apply plugin: "com.google.firebase.firebase-perf"
apply plugin: 'io.fabric'
import com.android.build.OutputFile
project.ext.react = [
entryFile: "index.js",
// Sometimes (like if you use Android API<17) adb forwards don't work, so you need a bundle in the dev APK
bundleInDebug: project.hasProperty("bundleInDebug") ? project.getProperty("bundleInDebug") : false,
]
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 rootProject.ext.compileSdkVersion
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
defaultConfig {
applicationId "com.kunstmuseum.kunstmuseum"
minSdkVersion rootProject.ext.minSdkVersion
targetSdkVersion rootProject.ext.targetSdkVersion
versionCode 5
versionName "1.4"
// Needed to support API<21, though there is a small chance proguard shrinks things sufficiently
multiDexEnabled true
}
splits {
abi {
reset()
enable enableSeparateBuildPerCPUArchitecture
universalApk false // If true, also generate a universal APK
include "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
}
}
signingConfigs {
release {
if (project.hasProperty('MYAPP_UPLOAD_STORE_FILE')) {
storeFile file(MYAPP_UPLOAD_STORE_FILE)
storePassword MYAPP_UPLOAD_STORE_PASSWORD
keyAlias MYAPP_UPLOAD_KEY_ALIAS
keyPassword MYAPP_UPLOAD_KEY_PASSWORD
}
}
}
buildTypes {
release {
minifyEnabled enableProguardInReleaseBuilds
proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
signingConfig signingConfigs.release
}
}
// applicationVariants are e.g. 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, "arm64-v8a": 3, "x86_64": 4]
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
}
}
}
}
dependencies {
implementation project(':react-native-zip-archive')
implementation project(':react-native-proximity')
implementation project(':react-native-webview')
implementation project(':rn-fetch-blob')
implementation project(':react-native-video')
implementation project(':react-native-svg')
implementation project(':react-native-sound')
implementation project(':react-native-shake')
implementation project(':react-native-audio-jack')
implementation project(':@react-native-community_async-storage')
implementation project(':react-native-gesture-handler')
implementation fileTree(dir: "libs", include: ["*.jar"])
implementation "com.facebook.react:react-native:+" // From node_modules
/* ----------------------------
* REACT NATIVE FIREBASE
* ---------------------------- */
// Library as defined in settings.gradle
implementation project(path: ':react-native-firebase')
// Required dependencies
//noinspection GradleCompatible
implementation "com.google.firebase:firebase-core:16.0.9"
implementation "com.google.android.gms:play-services-base:16.1.0"
/* -------------------------
* OPTIONAL FIREBASE SDKS
* ------------------------- */
implementation('com.google.firebase:firebase-ads:15.0.1') {
// exclude `customtabs` as the support lib version is out of date
// we manually add it as a dependency below with a custom version
exclude group: 'com.android.support', module: 'customtabs'
}
// Authentication
implementation "com.google.firebase:firebase-auth:17.0.0"
// Analytics
implementation "com.google.firebase:firebase-analytics:16.5.0"
// Performance Monitoring
implementation "com.google.firebase:firebase-perf:17.0.0"
// Remote Config
implementation "com.google.firebase:firebase-config:17.0.0"
// Cloud Storage
implementation "com.google.firebase:firebase-storage:17.0.0"
// Dynamic Links
implementation "com.google.firebase:firebase-dynamic-links:17.0.0"
// Real-time Database
implementation "com.google.firebase:firebase-database:17.0.0"
// Cloud Functions
implementation "com.google.firebase:firebase-functions:17.0.0"
// Cloud Firestore
implementation "com.google.firebase:firebase-firestore:19.0.2"
// Cloud Messaging / FCM
implementation "com.google.firebase:firebase-messaging:18.0.0"
// Crashlytics
implementation('com.crashlytics.sdk.android:crashlytics:2.9.9@aar') {
transitive = true
}
/* --------------------------------
* OPTIONAL SUPPORT LIBS
* -------------------------------- */
// Needed to support API<21, though there is a small chance proguard shrinks things sufficiently
implementation "com.android.support:multidex:1.0.3"
// For Firebase Ads
//noinspection GradleCompatible
implementation "com.android.support:customtabs:27.1.1"
// For React Native Firebase Notifications
implementation 'me.leolin:ShortcutBadger:1.1.22@aar'
// For animated GIF support
implementation 'com.facebook.fresco:animated-gif:1.10.0'
}
// 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'
}
apply plugin: 'com.google.gms.google-services'
您应该使用 英语 描述您的应用以及其他语言环境。
它显示 Dutch,这可能会影响搜索结果。
此外,搜索结果取决于多个因素,例如 下载、评论 等。谢谢
我们最近遇到了同样的问题。这似乎是新 google 开发者帐户上新应用程序的一些错误。我认为 google 已经改变了它的政策,现在更加重视新的开发者帐户。对我来说,只有一件事至少在一段时间内帮助解决了这个问题,如下所示:
转到您的 Google Play 管理中心> 定价和分发
应该说您的应用在所有国家/地区都可用。编辑它并使该应用程序在所有国家/地区不可用。
- 现在再次在所有国家/地区提供该应用程序并提交更新。
- 几分钟后您的更新就会生效,希望您的应用程序会出现在 Play 商店中。
注意:如果我在网络浏览器的 Play 商店中未登录我的 google 帐户就搜索了您的应用程序名称,它会出现在 no. 8 我猜,但是当我再次登录并在 Playstore 中搜索您的应用时,它消失了。这种情况也发生在我身上。
我的应用程序遇到了同样的问题,所以我向 Google 支持团队发送了一条消息来解决这个问题。
不幸的是,如果它是一个新应用程序,他们说算法可能需要几天(最多 2 周)才能检测到该应用程序并将其正确包含在搜索结果中。加快此过程的方法是通过直接 link 安装获得更多应用安装和评论。
我也遇到了同样的问题。
搜索页面刷新两周后,我写信支持。
这是一个答案:
I understand that you're concerned about your app's visibility on the
Play store.
Please note, we show a limited number of search results in Google Play
to ensure the best user experience. If your app's search rank for a
specific term is too low, your app will not display in results. Keep
in mind, however, that your app is always available by direct
link https://play.google.com/store/apps/details?id=com.johnpopov.bredogenerator&gl=vg,
which you can share with users as you actively market your app.
Many factors go into the Google Play search results, and while you
can’t control all of them, you can try to find the app by searching
pname:com.johnpopov.bredogenerator at play.google.com/store/apps. This
is a tip that helps you verify if your app is correctly included in
the search index.
As long as you can find the app with the prefix of pname, you can be
assured that the app is indexed.
所以,我想唯一的方法是直接安装更多广告 link。
我们为我们的客户创建了一个应用程序,该应用程序必须在 10 月 11 日之前可用。该应用程序已在 iOS 应用程序商店中可用,但 Google 播放似乎有问题。
我已将软件包添加到 9 月 26 日的发布轨道,希望它能在不久后得到审核和发布,幸运的是,它确实做到了。 我可以对应用程序(取自游戏控制台)使用 direct link,这表明它已正确发布。控制台没有列出任何错误。 设备和国家/地区设置已经过仔细检查,一切似乎都是正确的。
Google 几天前联系了支持,但不幸的是,他们仍然没有回复。
随着截止日期的临近,我每晚的睡眠越来越少。
有没有人对这个特定问题有任何经验并希望找到解决方案?
备注
- 应用是使用 React Native 版本 0.59.9 创建的
- 没有广告,但使用 AdMob SDK for Firebase Analytics
- 包名称是 "com.kunstmuseum.kunstmuseum"
- 在 Play 商店中搜索:"pub:Kunstmuseum Den Haag" 确实给了我一个结果。
AndroidManifest.xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.kunstmuseum.kunstmuseum"
android:versionCode="1"
android:versionName="1.0">
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<application
android:name=".MainApplication"
android:allowBackup="true"
android:label="@string/app_name"
android:icon="@mipmap/ic_launcher"
android:roundIcon="@mipmap/ic_launcher_round"
android:theme="@style/AppTheme">
<activity
android:name=".MainActivity"
android:label="@string/app_name"
android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
android:screenOrientation="portrait"
android:windowSoftInputMode="adjustResize">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
<service android:name="io.invertase.firebase.messaging.RNFirebaseMessagingService">
<intent-filter>
<action android:name="com.google.firebase.MESSAGING_EVENT" />
</intent-filter>
</service>
<service android:name="io.invertase.firebase.messaging.RNFirebaseInstanceIdService">
<intent-filter>
<action android:name="com.google.firebase.INSTANCE_ID_EVENT" />
</intent-filter>
</service>
</application>
build.gradle
apply plugin: "com.android.application"
apply plugin: "com.google.firebase.firebase-perf"
apply plugin: 'io.fabric'
import com.android.build.OutputFile
project.ext.react = [
entryFile: "index.js",
// Sometimes (like if you use Android API<17) adb forwards don't work, so you need a bundle in the dev APK
bundleInDebug: project.hasProperty("bundleInDebug") ? project.getProperty("bundleInDebug") : false,
]
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 rootProject.ext.compileSdkVersion
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
defaultConfig {
applicationId "com.kunstmuseum.kunstmuseum"
minSdkVersion rootProject.ext.minSdkVersion
targetSdkVersion rootProject.ext.targetSdkVersion
versionCode 5
versionName "1.4"
// Needed to support API<21, though there is a small chance proguard shrinks things sufficiently
multiDexEnabled true
}
splits {
abi {
reset()
enable enableSeparateBuildPerCPUArchitecture
universalApk false // If true, also generate a universal APK
include "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
}
}
signingConfigs {
release {
if (project.hasProperty('MYAPP_UPLOAD_STORE_FILE')) {
storeFile file(MYAPP_UPLOAD_STORE_FILE)
storePassword MYAPP_UPLOAD_STORE_PASSWORD
keyAlias MYAPP_UPLOAD_KEY_ALIAS
keyPassword MYAPP_UPLOAD_KEY_PASSWORD
}
}
}
buildTypes {
release {
minifyEnabled enableProguardInReleaseBuilds
proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
signingConfig signingConfigs.release
}
}
// applicationVariants are e.g. 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, "arm64-v8a": 3, "x86_64": 4]
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
}
}
}
}
dependencies {
implementation project(':react-native-zip-archive')
implementation project(':react-native-proximity')
implementation project(':react-native-webview')
implementation project(':rn-fetch-blob')
implementation project(':react-native-video')
implementation project(':react-native-svg')
implementation project(':react-native-sound')
implementation project(':react-native-shake')
implementation project(':react-native-audio-jack')
implementation project(':@react-native-community_async-storage')
implementation project(':react-native-gesture-handler')
implementation fileTree(dir: "libs", include: ["*.jar"])
implementation "com.facebook.react:react-native:+" // From node_modules
/* ----------------------------
* REACT NATIVE FIREBASE
* ---------------------------- */
// Library as defined in settings.gradle
implementation project(path: ':react-native-firebase')
// Required dependencies
//noinspection GradleCompatible
implementation "com.google.firebase:firebase-core:16.0.9"
implementation "com.google.android.gms:play-services-base:16.1.0"
/* -------------------------
* OPTIONAL FIREBASE SDKS
* ------------------------- */
implementation('com.google.firebase:firebase-ads:15.0.1') {
// exclude `customtabs` as the support lib version is out of date
// we manually add it as a dependency below with a custom version
exclude group: 'com.android.support', module: 'customtabs'
}
// Authentication
implementation "com.google.firebase:firebase-auth:17.0.0"
// Analytics
implementation "com.google.firebase:firebase-analytics:16.5.0"
// Performance Monitoring
implementation "com.google.firebase:firebase-perf:17.0.0"
// Remote Config
implementation "com.google.firebase:firebase-config:17.0.0"
// Cloud Storage
implementation "com.google.firebase:firebase-storage:17.0.0"
// Dynamic Links
implementation "com.google.firebase:firebase-dynamic-links:17.0.0"
// Real-time Database
implementation "com.google.firebase:firebase-database:17.0.0"
// Cloud Functions
implementation "com.google.firebase:firebase-functions:17.0.0"
// Cloud Firestore
implementation "com.google.firebase:firebase-firestore:19.0.2"
// Cloud Messaging / FCM
implementation "com.google.firebase:firebase-messaging:18.0.0"
// Crashlytics
implementation('com.crashlytics.sdk.android:crashlytics:2.9.9@aar') {
transitive = true
}
/* --------------------------------
* OPTIONAL SUPPORT LIBS
* -------------------------------- */
// Needed to support API<21, though there is a small chance proguard shrinks things sufficiently
implementation "com.android.support:multidex:1.0.3"
// For Firebase Ads
//noinspection GradleCompatible
implementation "com.android.support:customtabs:27.1.1"
// For React Native Firebase Notifications
implementation 'me.leolin:ShortcutBadger:1.1.22@aar'
// For animated GIF support
implementation 'com.facebook.fresco:animated-gif:1.10.0'
}
// 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'
}
apply plugin: 'com.google.gms.google-services'
您应该使用 英语 描述您的应用以及其他语言环境。 它显示 Dutch,这可能会影响搜索结果。
此外,搜索结果取决于多个因素,例如 下载、评论 等。谢谢
我们最近遇到了同样的问题。这似乎是新 google 开发者帐户上新应用程序的一些错误。我认为 google 已经改变了它的政策,现在更加重视新的开发者帐户。对我来说,只有一件事至少在一段时间内帮助解决了这个问题,如下所示:
转到您的 Google Play 管理中心> 定价和分发
应该说您的应用在所有国家/地区都可用。编辑它并使该应用程序在所有国家/地区不可用。
- 现在再次在所有国家/地区提供该应用程序并提交更新。
- 几分钟后您的更新就会生效,希望您的应用程序会出现在 Play 商店中。
注意:如果我在网络浏览器的 Play 商店中未登录我的 google 帐户就搜索了您的应用程序名称,它会出现在 no. 8 我猜,但是当我再次登录并在 Playstore 中搜索您的应用时,它消失了。这种情况也发生在我身上。
我的应用程序遇到了同样的问题,所以我向 Google 支持团队发送了一条消息来解决这个问题。
不幸的是,如果它是一个新应用程序,他们说算法可能需要几天(最多 2 周)才能检测到该应用程序并将其正确包含在搜索结果中。加快此过程的方法是通过直接 link 安装获得更多应用安装和评论。
我也遇到了同样的问题。 搜索页面刷新两周后,我写信支持。 这是一个答案:
I understand that you're concerned about your app's visibility on the Play store.
Please note, we show a limited number of search results in Google Play to ensure the best user experience. If your app's search rank for a specific term is too low, your app will not display in results. Keep in mind, however, that your app is always available by direct link https://play.google.com/store/apps/details?id=com.johnpopov.bredogenerator&gl=vg, which you can share with users as you actively market your app.
Many factors go into the Google Play search results, and while you can’t control all of them, you can try to find the app by searching pname:com.johnpopov.bredogenerator at play.google.com/store/apps. This is a tip that helps you verify if your app is correctly included in the search index.
As long as you can find the app with the prefix of pname, you can be assured that the app is indexed.
所以,我想唯一的方法是直接安装更多广告 link。