I have the same problem. My workaround was to change the frame rate of my galaxy note 9 to 60 when taking videos in full hd. Then I adjusted the custom rate so it matches the frame rate of 59.06 because the windows file properties shows this rate. Didn't even bother to see the real precise frame rate in VLC because the number would be somewhat of 59.060004001. This setup gave me a little longer audio than the video. The difference is so minor that even in long videos it's unnoticeable, I just cut the end of the audio so it matches the video. To me it's clearly a bug. It's supposed to identify the floating frame rate just like in Shotcut, there the videos are perfect, in Blender for some reason you have to work around it....