Android alpha 测试“找不到项目”

Android alpha testing "Item not found"

提问by Arunita

I have published my app for alpha testing, but not able to download it from play store.

我已经发布了我的应用程序进行 alpha 测试，但无法从 Play 商店下载它。

I have opened the url "https://play.google.com/apps/testing/com.*" and accepted to be a tester and now it shows me "you are a tester". But when I click on the link "download it from the Play Store", it shows me "Item not found" in my test device play store and "requested URL was not found" in desktop browser.

我打开了网址“ https://play.google.com/apps/testing/com. *”并接受成为测试人员，现在它向我显示“你是一名测试人员”。但是，当我单击“从 Play 商店下载”链接时，它在我的测试设备 Play 商店中显示“找不到项目”，而在桌面浏览器中显示“找不到请求的 URL”。

1. App is in published state for more than 48 hours.
2. App is published in all countries.
3. google groups for testers are added, I can see the group in manage testers tab. Tester account is added to the group ( triple checked it)
4. test device has only one tester account.
5. I can access the in-app purchases, which means the app is published properly. Google doesn't support draft mode anymore.

1. 应用处于已发布状态超过 48 小时。
2. 应用程序在所有国家/地区发布。
3. 添加了测试人员的 google 组，我可以在管理测试人员选项卡中看到该组。测试者帐户已添加到组中（三重检查）
4. 测试设备只有一个测试员账号。
5. 我可以访问应用内购买，这意味着应用已正确发布。Google 不再支持草稿模式。

I went through some similar posts in stackoverflow, but there is no definite answer. Looks like for some people it resolved automatically and some people are not lucky enough.

我在 stackoverflow 中浏览了一些类似的帖子，但没有明确的答案。看起来对于某些人来说它会自动解决，而有些人则不够幸运。

回答by educoutinho

If the app is "Published", but when you click in "View in play store" the site (example: https://play.google.com/store/apps/details?id=com.companyname.appname) show the error:

如果应用已“已发布”，但当您点击“在 Play 商店中查看”时，网站（例如：https: //play.google.com/store/apps/details?id=com.companyname.appname）会显示错误：

"We're sorry, the requested URL was not found on this server",

“很抱歉，在此服务器上找不到请求的 URL”,

try this:

尝试这个：

• In "Google Play Console" (https://play.google.com/apps/publish), select your app
• goto menu: Release management / App releases
• In Aplha, click in the button "Manage Alpha"
• Click in "Manage testers" and copy the link "Opt-in URL" (example: https://play.google.com/apps/testing/com.companyname.appname)
• Send this link to your alpha users, you and the users need to click in "Became a tester" before access the app in PlayStore.

• 在“Google Play 管理中心”( https://play.google.com/apps/publish) 中，选择您的应用
• 转到菜单：发布管理/应用发布
• 在 Aplha 中，单击“管理 Alpha”按钮
• 单击“管理测试人员”并复制链接“选择加入 URL”（例如：https: //play.google.com/apps/testing/com.companyname.appname）
• 将此链接发送给您的 alpha 用户，您和用户需要先点击“成为测试员”，然后才能在 PlayStore 中访问该应用程序。

After this, open the link of app in play store again (View in play store) logged with a user from the testers list.

之后，再次打开使用测试人员列表中的用户登录的应用商店链接（在游戏商店中查看）。

If the url still don't open, try close your browser, or clear the browser cache and try again. The browser store a cache of redirects.

如果 url 仍未打开，请尝试关闭浏览器，或清除浏览器缓存并重试。浏览器存储重定向缓存。

回答by Vladimir Makhaev

If you are using Chrome, then it caches redirects. To fix it, clear browsing data. More details on this

如果您使用的是 Chrome，那么它会缓存重定向。要修复它，请清除浏览数据。更多详情

回答by Nycen

In my case, the issue was that I wasn't logged to Google with the proper account in Chrome.

就我而言，问题是我没有在 Chrome 中使用正确的帐户登录到 Google。

I cleared all browsing data, but un-logging from Gmail/Google and re-logging with the proper @gmail.com account would probably have done the trick.

我清除了所有浏览数据，但是从 Gmail/Google 取消登录并使用正确的 @gmail.com 帐户重新登录可能会成功。

回答by unludo

For my part it was due to the fact that I sent the link through SMS. It worked when I sent it by email. This link has the form https://play.google.com/apps/testing/com.*. This is this link that you have to share by email.

就我而言，这是因为我通过短信发送了链接。当我通过电子邮件发送它时它起作用了。此链接的格式为https://play.google.com/apps/testing/com.*。这是您必须通过电子邮件共享的链接。

回答by BobV

Another thing to check is whether or not Pricing & Distribution -> Only make this application available to my organizationis checked. It seems that this doesn't interact well with Alpha- or Beta-only tests, even if your test account is in the given domain. Once I turned this flag off, my beta-only app became visible via the Play Store link from the testing signup page.

要检查的另一件事是是否Pricing & Distribution -> Only make this application available to my organization已检查。即使您的测试帐户在给定的域中，这似乎也与仅 Alpha 或 Beta 测试无法很好地交互。一旦我关闭了这个标志，我的测试版应用程序就可以通过测试注册页面的 Play 商店链接看到。

回答by Pinky Walve

This can be due to a silly mistake where you aren't signed in with the appropriate Google Play account in your device's Google Play Store.

这可能是由于一个愚蠢的错误造成的，即您没有在设备的 Google Play 商店中使用相应的 Google Play 帐户登录。

Sign in with the testing gmail account into Google Play and then click on the test-link

使用测试 Gmail 帐户登录 Google Play，然后单击测试链接

For more detail check Item not found

有关更多详细信息，请检查未找到项目

回答by Alexey Kurilov

Where you add groups for test - there have a link for tester (something like terms) you need to click this link on each testing device and say "Yes"

在添加测试组的地方 - 有一个测试员链接（类似于术语），您需要在每个测试设备上单击此链接并说“是”

After that link apear in market. I wait 3 days before found it : )

在那个链接出现在市场之后。我等了 3 天才找到它:)

回答by Abdul Waheed

I had this similar issue.In my case, I had multiple testers as CSV and there was an space between multiple users tester.Space was the issue in email address.Bad email address may cause this problem.

我有这个类似的问题。在我的例子中，我有多个测试者作为 CSV 并且多个用户测试者之间有一个空格。空格是电子邮件地址的问题。电子邮件地址错误可能会导致这个问题。

回答by Bruno Girin

In addition to all the great answers here, I just found out that if you did an internal test before the closed (alpha) test, the Play Store may want you to use the internal test URL instead.

除了这里所有的好答案之外，我刚刚发现，如果您在封闭 (alpha) 测试之前进行了内部测试，Play 商店可能希望您改用内部测试 URL。

So say you have your great app and you released it to the internal test track. You created a list called "Internal Testers" for that track and it all went swimmingly. When you did this, Google Play gives you a URL for those testers of the form https://play.google.com/apps/internaltest/{id}. Your internal testers joined the program using that URL, downloaded the app no problem and the test went through.

假设您拥有出色的应用程序，并将其发布到内部测试轨道。您为该曲目创建了一个名为“内部测试员”的列表，并且一切顺利。当您执行此操作时，Google Play 会为您提供这些形式为 的测试人员的 URL https://play.google.com/apps/internaltest/{id}。您的内部测试人员使用该 URL 加入了该程序，下载应用程序没有问题，并且测试通过了。

You now upgrade to the closed track (alpha testing). You create a new list called "Alpha Testers" with new people in it and you enable your release both for "Internal Testers" and "Alpha Testers" thinking that you should carry over your internal testers to alpha. When you do this, Google Play gives you a URL of the form https://play.google.com/apps/testing/{package}. Your alpha testers can now join the program using that URL and download the app. But your internal testers have to keep using the internal test URL to join the program.

您现在升级到封闭轨道（alpha 测试）。您创建了一个名为“Alpha 测试员”的新列表，其中包含新人员，并为“内部测试员”和“Alpha 测试员”启用您的版本，认为您应该将内部测试员转移到 Alpha 版。执行此操作时，Google Play 会为您提供表单的 URL https://play.google.com/apps/testing/{package}。您的 Alpha 测试人员现在可以使用该 URL 加入该计划并下载该应用程序。但是您的内部测试人员必须继续使用内部测试 URL 来加入该计划。

From testing a variety of scenarios, it looks like moving a tester from on list to another doesn't fix the problem.

从测试各种场景来看，似乎将测试人员从列表移动到另一个并不能解决问题。

As far as I can tell the Google Play documentation doesn't mention any of this.

据我所知，Google Play 文档没有提到任何这些。

回答by mrerdem

Also, make sure the device you are using is among the supported devices for your app. For this, check Release management -> Device catalogon play console.

此外，请确保您使用的设备是您的应用程序支持的设备之一。为此，请检查Release management -> Device catalog播放控制台。

If this is the problem, expect to see a warning similar to the app is not compatible with your devicewhen you visit play store page via a web browser and Item not founderror via play store app.

如果这是问题所在，预计会看到类似于the app is not compatible with your device您通过网络浏览器访问 Play 商店页面和Item not found通过 Play 商店应用程序访问错误时的警告。

In my case, I had to make some changes in the Manifest to correct the list of supported devices. So, I replaced below line causing the number of supported devices to be 0:

就我而言，我必须在 Manifest 中进行一些更改以更正支持的设备列表。因此，我替换了以下行，导致支持的设备数为 0：

    <uses-feature android:name="android.hardware.camera2.full" />

with:

和：

    <uses-feature android:name="android.hardware.camera2.full" android:required="false" />

In your case, Manifest may need a different change of course.

在您的情况下，Manifest 当然可能需要不同的更改。