@accounts6 is this a new application you are setting up? Were you using a previous version of Lock and now using Lock 11.7.0 you are experiencing this issue?
Are you initiating the authentication request from localhost while passing the prompt=none parameter? If this is the case, please take a look at our documentation regarding skipping consent for first-party clients.