This issue is fired when the username/password combination that protects your test version is the default combination:
Username: username
Password: password
It is considered an issue because every Bubble developer knows it is the default combination and could easily guess it and access your test version.
Solution
To fix this issue, you should define a username/password combination that is not the default one and is complicated enough so that other people can't guess it easily.
The best practice for this is to generate a random username generator, like this one.
You'll end up having a username/password combination that looks like this:
Username: $Up%Dl@479L2yOxi
Password: *WUgmv5648*iNYWy
