在Android市场发布测试版
我想在 Android 市场上发布我的某些应用程序的测试版，但面临着我无法两次上传具有相同包名的应用程序的问题 - 甚至不能具有不同的证书。但是，发布版和测试版有 2 个包名称会带来很多麻烦（例如，每次都必须更改对 R 不同位置的引用）
是否有一个最佳实践/好的解决方法来解决该问题？
I want to publish a beta version of some app of mine on the android market and face the problem that I cannot upload an app with the same package-name twice - not even with a different certificate. But having 2 package-names for release and beta version makes a lot of trouble ( e.g. having to change references to the different location of R every time )
Is there a best-practice/good workaround for that problem?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
是的，调用您的包
修复此应用程序中的所有错误。然后，当您上线时，只需复制项目重构您的包名称（项目上的 Eclipse CTRL+ALT+R）更新您的清单并重新-发布。然后，您将不再支持测试版软件包，您甚至可以单击“取消发布”，或者发布一个更新，该更新显示链接到新软件包的升级屏幕（即新的市场 url）
有什么问题？
Yes call your package
Fix all the bugs in this app. Then when you go live just copy the project refactor your package name (Eclipse CTRL+ALT+R on the item) update your manifest and re-release. The beta package is then not supported by you any more and you can even click unpublish, or release an update that shows an upgrade screen linking to the new package (i.e. new market url)
What's the problem?
自 IO 2013 以来，现在有一种选项可以进行 beta 测试：
https://support.google.com/googleplay/android-developer/answer/3131213? hl=zh-cn
since IO 2013 there is now one option to do beta-testing:
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
我们上传但不发布应用程序的测试版。一旦上传，市场将假设任何传入的许可证检查都是从侧面加载的合法安装完成的，并将响应“已许可”。因此，我们的 Beta 测试人员可以测试完整的实现，包括许可代码。 （对于已上传但未发布的应用程序，测试帐户响应也会受到尊重。）
测试完成后，我们使用相同的包（和签名证书）上传发布版本，然后发布。
We upload but do not publish beta versions of our apps. Once uploaded, the market will assume that any incoming license check is being done from a legitimate installation that was side loaded and will respond "licensed". So our beta testers can test a full implementation, including the licensing code. (Test account responses are also honored for uploaded but unpublished apps.)
When the testing is complete, we upload the release version using the same package (and signing cert), and publish.
我偶然发现了这个讨论 Android Beta 测试的博客，我觉得这是更好的方法。所以就跟大家分享一下。希望对大家有所帮助。 http://zubhium.posterous.com/android-app-beta-testing
使用 com.packagename.beta 推送应用程序并不是一个好主意。它会造成不必要的混乱，其次，您不希望在市场上获得不稳定的版本，从而使您的品牌获得不好的评价。
I came across this blog which discuss Android Beta Testing and feels like that the better way. So just sharing with you guys. Hopefully it will be helpful for all . http://zubhium.posterous.com/android-app-beta-testing
Pushing app with com.packagename.beta is not a very good idea. It creates unnecessary confusion and secondly you don't want to get unstable version in market to get bad ratings for your brand.
为什么不能为发布版本使用相同的包名称？这样做还可以让您的测试版用户收到“应用程序升级”（即最终版本的发布）的通知。
如果您确实想使用不同的包名称，一种方法是制作一个可以运行的 ant 脚本，该脚本会更改所有导入和 manifest.xml，以使用新名称。因此，您拥有自己开发的代码，然后只要准备好上传到市场，就可以运行 ant 脚本；说“蚂蚁贝塔”。这会将您的所有包从 com.company.app 重命名为 com.company.app_beta，您可以在市场上发布它。
Why can't you just use the same package name for the release version? Doing so would also let your beta users get notified of an "application upgrade" (that is, the release of the final version).
If you do want to use different package names, one way is to make an ant script that you can run that changes all the imports, and the manifest.xml, to use the new name. So you have your code that you develop in, then you can just run your ant script whenever you're ready to upload to the Market; say "ant beta". This would rename all your packages from com.company.app to com.company.app_beta, and you could release it on the Market.
最好不要将测试版上传到市场。您应该只将生产就绪的应用程序上传到市场，因为这是用户所期望的。
如果您想对您的应用程序进行 Beta 测试，最好使用私人分发渠道。
如果您使用相同的证书，则具有相同包名称的应用程序将被视为对前一个应用程序的更新。用户将能够轻松更新。
It is good practice not to upload a beta version to the Market. You should only upload production ready applications to the Market, as this is what the users expect.
If you want to beta test your application, it is better to use a private distribution channel.
If you use the same certificate, then an application with the same package name will be considered as an update to a previous one. Users will be able to update easily.