1. Download our Official Android App: Forums for Android!

Apps Publish New Version of App on Google Play - How To?

Discussion in 'Android Development' started by ac4android, Apr 4, 2016.

  1. ac4android

    ac4android Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    53
    Posts:
    198
    Joined:
    Nov 3, 2015

    Nov 3, 2015
    198
    29
    53
    I need this last step in beta testing, which is to upload and publish a new version and send notification to tester. versionCode 2
    versionName "1.1"

    I got this error when I tried to publish the new version:
    This configuration cannot be published for the following reason(s):

    • Version 1 is not served to any device configuration: all devices that might receive version 1 would receive version 2.
    My testers cannot load the new version, nor do they get a notice that there is a new version.
    Yes, I read the instructions and followed them.
    What do I have to do to get this working ?

     

    Advertisement

  2. Brian706

    Brian706 I like turtles!
    Moderator
    Rank:
     #26
    Points:
    1,053
    Posts:
    9,345
    Joined:
    Jul 25, 2012

    Jul 25, 2012
    9,345
    8,589
    1,053
    Drafter
    The-Truth and scary alien like this.
  3. ac4android

    ac4android Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    53
    Posts:
    198
    Joined:
    Nov 3, 2015

    Nov 3, 2015
    198
    29
    53
    Thx. In the meantime, I'll try and remove the new beta-app and upload it again with a new release.apk, same key of course

    Here is an screen-shot of the error message. I don't know what Google means by it.

    UploadError3.JPG
     
  4. Brian706

    Brian706 I like turtles!
    Moderator
    Rank:
     #26
    Points:
    1,053
    Posts:
    9,345
    Joined:
    Jul 25, 2012

    Jul 25, 2012
    9,345
    8,589
    1,053
    Drafter
    After a quick Google search, it sounds like you need to deactivate the old version first. Under actions on version 1 click the dropdown menu and see if there is an option to deactivate that version, then the new version should become ready to publish.
     
    The-Truth, scary alien and ac4android like this.
  5. ac4android

    ac4android Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    53
    Posts:
    198
    Joined:
    Nov 3, 2015

    Nov 3, 2015
    198
    29
    53
    Yes, that seems to have worked.

    The trick is to unpublish the older version first, then submit update, the missing step in Google's instructions. I dread to deviate from the standard Google "to-do" for fear of life and limb.

    Now let's wait 24 hours to see whether my testers get a notification of a new version.
     
    The-Truth, scary alien and Brian706 like this.
  6. Brian706

    Brian706 I like turtles!
    Moderator
    Rank:
     #26
    Points:
    1,053
    Posts:
    9,345
    Joined:
    Jul 25, 2012

    Jul 25, 2012
    9,345
    8,589
    1,053
    Drafter
    Great news! Thanks for keeping us updated!
     
    The-Truth and scary alien like this.
  7. scary alien

    scary alien not really so scary
    Moderator
    Rank:
     #8
    Points:
    2,138
    Posts:
    22,298
    Joined:
    Mar 5, 2010

    Mar 5, 2010
    22,298
    23,695
    2,138
    Male
    space alien ;)
    Indy
    Sorry I missed the ping, @Brian706 (finally saw it in my email)...

    I haven't yet used beta apk publishing function--I simply rely on the "normal" publish-to-production methods where the currently published apk gets deactivated and the new one get's published.

    It sounds like with a beta apk testing that you must manage that yourself (i.e., disable/deactivate a prior apk and activate/enable the new one).

    Glad you got things sorted with Brian's help, @ac4android! :)

    Cheers!
     
    The-Truth and Brian706 like this.

Share This Page

Loading...