As defined in the codex,
If version is set to false, a version number is automatically added equal to current installed WordPress version. If set to null, no version is added.
You're currently setting false. You should be setting null:
wp_enqueue_script('myID', $url, array('jquery'), null, true);
Change the 4th parameter from false to null.
wp_enqueue_script( 'myID', $url, array( 'jquery' ), null, true );
From the wp_enqueue_script() documentation:
(string|bool|null) (Optional) String specifying script version number, if it has one, which is added to the URL as a query string for cache busting purposes. If version is set to false, a version ...
There are two possible solutions depending on what kind of relationship you expect to have with the people that use the plugin.
Instruct them how to create an app and which URLs to use to be compatibe with what you expect in the plugin, have a setting page at the wordpress admin in which they can either upload the secrets file or configure the app secrets.
Did you try to exit; after the wp_redirect()?
“Note: wp_redirect() does not exit automatically, and should almost always be followed by a call to exit;”
With some playing around I realized I am definitely an idiot and WAY over-thought things. While I had previously read and tried some of the things in this similar post, I ended up substituting their code for mine and found it actually worked for my use case. In trying to understand why that was, I began trying to convert it to become mine and ...
The user_status field has long been no longer used in core, so maybe that's why there is no argument that will filter the users by their user_status value?
However, you can use the pre_user_query hook to alter the user query's SQL command, i.e. to add something like a AND user_status = 0 into the WHERE clause.
So for example, you can add this into your theme'...