To update this thread, we were able to identify that what was causing the issue was that the app contained Master scopes.
If the account you are using to authorize the app does not have a Master Account License associated with it, then this is expected.