The b2 CLI app behaves differently on macOS/Linux than it does on Windows when creating a key.
Versions tested: Up to 4.5.1

Reproducible example:

1. Authorize with master account.
2. Try to create a key with the following permissions:

b2 key create --bucket my-bucket-name-here Test-Write-Only-Key-Files-1 listBuckets,readBuckets,listFiles,readFiles,writeFiles,readBucketEncryption,readBucketReplications,readBucketRetentions,readFileRetentions,writeFileRetentions,readFileLegalHolds

When attempting a b2 account authorize with the key information yields the following error:
ERROR: unable to authorize account: This request is not currently supported on API version number 2 (bad_request)

Additionally, the key is hidden from the "Application Keys" portion of the web portal.

Running the same command on the Windows version creates the correct key as expected, allows authorization, and shows itself in the web portal.