Your statement is true for testing app licensing. When using a debugging
APK with higher version number than the currently uploaded one the LVL
still works for the debug version.
On Saturday, December 15, 2012 9:48:19 PM UTC-6, Raymond C. Rodgers wrote:
I may be mistaken, but I think that
On Sun, Dec 16, 2012 at 12:48 PM, Raymond C. Rodgers
raym...@badlucksoft.com wrote:
I may be mistaken, but I think that with the first apk uploaded to test
with, you can then distribute updated debug copies outside of the Play
Store/developer console and the correct (or at least updated)
Aaaah, I see now. Okay. Thanks.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
I'm debugging in-app purchases. This requires me to create the app profile
on the console and upload the apk (but not necessarily publish it). With
an invited test gmail account, I can then test in-app purchases. The
problem is, there is no way to upload changes to the app if I have to fix
In your manifest you should have both android:versionCode and
android:versionName attributes. The versionCode is the one you need to
increment but the versionName is the one the user sees and that one
can be whatever you like afaik.
On Sat, Dec 15, 2012 at 10:15 PM, Keith Wiley kbwi...@gmail.com
Yeah, I know, but I still want to use the versionCode to label public
releases, not just one-off momentary debug versions. I'm not even talking
about officially versioned betas here, I'm just talking about pushing the
code through a rapid build-test-debug-fix cycle. Every time I want to try
I may be mistaken, but I think that with the first apk uploaded to test
with, you can then distribute updated debug copies outside of the Play
Store/developer console and the correct (or at least updated) behavior
will be exhibited in those debug copies. As far as I know, you only need
to have
7 matches
Mail list logo
