Doesn't work with renamed apks

[ursusursus]

Hi, we rename our release apks like this

applicationVariants.all { variant ->
        variant.outputs.all { output ->
            if (variant.buildType.name == "debug") return

            // Rename APK
            def variantName = variant.name
            def date = new Date().format("dd-MM-yyyy")
            def versionName = variant.versionName.replace(".", "-")
            def versionCode = output.versionCodeOverride
            def version = "v${versionName}_${versionCode}"
            def gitHash = getGitHash()

            outputFileName = "app_tm__${variantName}_${gitHash}__${date}__${version}.apk"
        }
    }

If I ran the uploadFooReleaseToBrowserstackAppLive it complains the apk is not found, even though it is there, but its renamed
If I disable the renaming, then it works fine

// agp 4.2.1, gradle 6.8.2, plugin 3.0.3

[Tae-juss]

The Browserstack plugin tries to identify the apk by searching for apks which have a name matching the variant base name generated. By default, android uses the variant base name for generating the apk name.

If you would like this to work for your setup, the workaround is that you need to inculcate the base name string in your custom name given to your app, it can be any name of your choice but must contain the base substring.

[ursusursus]

I don't follow. You want me to hardcode the default name as a prefix of my custom one?

Btw firebase app distribution; and gradle-play-publisher both do work out of the box, even with the name change, so probably looking for exact name is not a good idea, instead look for *.apk or something like that if possible

[o-hackee]

hello! faced the same issue, and not fancy changing the output file name. Any updates on that? maybe a new parameter or configuration?

[o-hackee]

hey, after looking through the source code of the plugin i've got an idea of overriding appVariantBaseName property:

applicationVariants.all { variant ->
    variant.outputs.all {
        outputFileName = "<some name pattern here><some version information>.apk"
    }
    tasks.named("execute${variant.name.capitalize()}TestsOnBrowserstack") {
        appVariantBaseName = "<some name pattern here>"
    }
    variant.testVariant?.outputs?.all {
        outputFileName = "<some name pattern here>-androidTest.apk"
    }
}

BrowserStack people, could you evaluate this approach please?

[arjun-krishna1994]

Hi ursusursus,
Could you try this new approach?

gradle build
gradle browserstackCLIWrapper -Pcommand="app-automate espresso run -a ""$appPath"  " -t ""$testSuitePath"

Where appPath is an environment variable which points to the local path of your app apk. You can follow the same naming pattern you have for your release APKs, i.e "app_tm__${variantName}_${gitHash}${date}${version}.apk"

testSuitePath is an environment variable which points to the local path of your test suite apk. Similar to the previous one you can use any naming pattern you need over here.

The second gradle command will just run the tests , from the apks built in the first gradle command. You can put in the renamed apk names dynamically by putting in the apk names in the -a option and -t option.

Please use the version 3.1.0 or higher of this gradle plugin for it to work. Hope this helps!