Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-62329

Problem with associating multiple expansion files with multiple APKs

      From GitHub: https://github.com/jenkinsci/google-play-android-publisher-plugin/pull/21#commitcomment-36647848

      I suspect this causes a regression (or is a breaking change, depends on the pov )

      I have a simple setup where I upload 2 apk for 2 arch of my app:
      MyApp*-arm-24-ObbYes.apk,MyApp-*-aarch64-24-ObbYes.apk
      The ARMV7 one has a version code ending with 01, and the AARCH64 ends with 11, so that the aarch64 is not masked.

      Accordingly, I upload 2 OBB's:
      main.*01.tv.myapp*.obb,main.*11.tv.myapp*.obb

      This used to work in 2.0, but now I get:

      Expansion filename 'main.2001022011.tv.myapp.obb' doesn't match the versionCode of any of APK(s) to be uploaded: 2001022001

      I think this commit causes it.
      Question is how to upload 2 different obb for 2 archs of the same app, now?

      I haven't yet looked into this at all, to figure out what the actual issue is. It sounds like it should work (and it was before the 3.0 release), but apparently not…

          [JENKINS-62329] Problem with associating multiple expansion files with multiple APKs

          There are no comments yet on this issue.

            orrc Christopher Orr
            orrc Christopher Orr
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: