Debugger breakpoint hitting on the same line in file but of the different build variant while using lambdas

We have many different builds, flavors and dimensions in our project. But after updating to Android Studio 3.5 we noticed a strange behavior that when we create a breakpoint in some lambda of our file that exists in more than one build variant then the debugger is not working properly and is being hit in the file (of the same name and package) of the different build variant. Interestingly this whole issue only happens when the breakpoint is set to be triggered in the body of the lambda and is working perfectly fine otherwise

So in summary to reproduce this issue, you have to:

1. Create two flavors and a file with the same name in each of these flavors
2. Create a code that contains lambda at some line X in both flavors

Now only one of the two things will happen but not both:

• When you are in flavor A and you create a trigger on line X it will break on the same line but in the file of flavor B
• When you are in flavor B and you create a trigger on line X it will break on the same line but in the file of flavor A

Here are some of the screenshots of when we tried to reproduce the issue:

ActualFlavor's AuthRepository (Active Build Variant):

DummyFlavor's AuthRepository:

So the question is what are we doing wrong? Or is it really an issue in Android Studio right now?

Android Studio version = 3.5 kotlin version = 1.3.50 build:gradle version = 3.5.1