We develop and publish our own apps as well as apps for others to publish on Google Play. Back when Google Play was Android Market, we used the following strategy for testing the licensing code in apps we developed for others:
- Upload (but do not publish) the app to our publisher account. The app included our publisher public key with the license check code.
- Test the app as we set different licensing responses through our developer console.
- When we were satisfied that everything was working properly, we deleted the uploaded app from our Android Market account. We could do this because the app had never been published.
- Change the publisher public key in the licensing code to that of our partner.
- Deliver the .apk to our partner to publish in their publisher account on Android Market. This worked because we had deleted the app from our Android Market account.
It's been the better part of a year since we did this. Does anyone know if the same strategy can be used with Google Play? In particular, do the parts in bold above still work? Is it still possible to complete remove all traces of an app that has been uploaded but never been published, so that someone else can then upload and publish it?
One alternative, which we will do if we must, is to change the app's package name for our license testing phase. However, this is complex and can introduce additional errors when we change the package name back.
Another alternative is for our partner to set up a user account for us. However, while user accounts can be restricted from viewing financial data, they cannot (as far as we can tell) be restricted to working with a single app. We can understand why partners would not want to allow such broad access.
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…