BITRISE PUBLIC INSTALL PAGE URL showing only unsigned apk

My android workflow generated Signed and unSigned apk files.
After successful workflow I am sending the BITRISE_PUBLIC_INSTALL_PAGE_URL to Slack.

When I selected the BITRISE_PUBLIC_INSTALL_PAGE_URL on Slack I am only getting unsigned apk file.

I need signed apk file.

Is there any variable that I can use to send only the Signed.apk file URL to slack.

1 Like

Hi @ramki1979,

If you don’t need the unsigned APK at all, then you can simply change the APK filter of the Gradle Runner step to not to include (exclude filters input) the unsigned APK - see: File already exists error

If you do need both to be attached to the build / deployed, but you only want a public install page for the signed on: please use two separate Deploy to steps, one for the unsigned APK and one for the signed one. Related #how-to : How to deploy only a specific Android APK? (Use multiple deploy steps and set specific path(s) section). This discussion might also help, in case you’d need the public install page of both: Public install page URLs for multiple apps

If you have any questions just let us know! :wink:

In my workflow Gradle only generated Released unsigned APK. After that I have a Bitrise Sign APK Step that generates the Signed APK. I think applying a filter wouldn’t help me.

Yes, that won’t, but the other solution, to specify the path in the Deploy to step (instead of just a directory) certainly does :wink:

The Sign APK step exports the signed APK’s path in both BITRISE_SIGNED_APK_PATH and BITRISE_APK_PATH env vars:

So setting the Deploy directory or file path (deploy_path) option of the Deploy to step to e.g. $BITRISE_SIGNED_APK_PATH should deploy only the signed APK and expose its public install page (similar to what’s described here Public install page URLs for multiple apps).

1 Like

Made the changes. Need to verify during the next build.

Thanks @viktorbenei for helping on this one.

1 Like

Let us know how it goes @ramki1979! :wink:

It was working.

1 Like