gradle-play-publisher: Wrong authentication file is set in multiple flavours project

Describe the bug

Hey, I have a project with multiple flavours and wrong authentication file is used when I specify authentication file for the exact flavour combination. Example of my configuration:

android {
   flavorDimensions("partner", "brand")
   productFlavors {
        register("special") {
            dimension = "partner"
        .....
        }
        register("default") {
            dimension = "partner"
        .....
        }

        register("first") {
            dimension = "brand"
        .....
        }

    buildTypes {
        getByName("debug") {
        .....
       }
        getByName("release") {
        .....
       }
   }

    play {
        releaseStatus.set(ReleaseStatus.DRAFT)
        enabled.set(false)
    }

    playConfigs {
        register("specialFirstRelease") {
            serviceAccountCredentials.set(SPECIAL_FIRST_KEY)
            enabled.set(true)
        }

        register("first") {
            serviceAccountCredentials.set(FIRST_KEY)
            enabled.set(true)
        }
    }
}

So when I run publishSpecialFirstReleaseBundle, FIRST_KEY is used instead of the expected SPECIAL_FIRST_KEY

How To Reproduce

Try to publish in a multi flavour project (as example above)

Versions

• Gradle Play Publisher: 3.2.0
• Gradle Wrapper: 7.0
• Android Gradle Plugin: 4.1.3

Tasks executed

publishSpecialFirstReleaseBundle

Expected behavior

Defined authentication file is used.