Empty platformBuildVersionName appearing in Android version name

Question & Answer Builds
1

Bitrise Build Issue Report template

Description of the issue

Just doing an Android build from a Cordova project. I have necessary keystore added to sign the apk.

Signed (release) apk is being generated, but the Version name for the apk is coming out as => 1.0.41’ platformBuildVersionName=’ (expected is just 1.0.41?)

Environment:

Hybrid (Xamarin, Ionic, …) on macOS, includes Visual Studio for Mac, Stable channel

Cordova Archive 1.1.1

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? :
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? :

Local reproduction

Can it be reproduced on your own Mac/PC by following our [local debug guide] -(How to debug your build locally / "It works on my Mac/PC but not on bitrise.io")? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.

Not reproducible in local cordova build

Build log

2

Hi @ilatif,

Thanks for your report! We’re aware of the problem and are already looking into it! :slightly_smiling_face:

Will make sure to update you here once the issue is resolved!

1 Like
3

@bitce

Hi, thanks for the prompt response !!! Any estimated timeline on this? I am about to demo/propose bitrise for a production delivery… I wish the issue was sth less obvious than a garbage version name :neutral_face:

4

Hi @ilatif!

Really sorry to hear about this inconvenience :frowning_face: Unfortunately nothing specific as an ETA would be yet, there’s a lot on our Tooling team’s plate, but we do understand this is a “very visible” issue and working on resolving it shortly.

1 Like
5

Hi @ilatif,

Is this still an issue with the latest versions of the steps? (Please make sure that you upgrade to the latest versions).

6

Still an issue. Using the latest version of the cordova archive step.

7

cordova archive 1.1.1

8

Hey @ilatif,

This issue was due to our Deploy to Bitrise.io step. Please upgrade that to the latest version, that will resolve this issue.

9

Fix confirmed with the latest deploy step. Thanks.

This thread can be closed.

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.