CLI create attachment bug

[ChristianTrolleMikkelsen]

Hi

We use Bitwarden cli a great deal and we recently decided to start uploading some attachments to some of our logins, by script.
When we call:

bw --session $sessionKey create attachment --file $pathToAttachment --itemid ($item.id)

We get the item returned but no where is the attachment visible.
The item is shared in an organization.
The user has write access to the collection in which the item resides.

Since there is nothing indicating an error has occoured we are stuck :).

Returned:
`
{
"object": "item",
"id": "X",
"organizationId": "Y",
"folderId": null,
"type": 1,
"name": "Z",
"notes": "-",
"favorite": false,
"login": {
"uris": [

],
"username": "-",
"password": "-",
"totp": "-",
"passwordRevisionDate": null

},
"collectionIds": [
"XYZ"
],
"revisionDate": "2019-03-29T14:12:20.800Z"
}
`

[kspearrin]

Does it actually create the attachment if you view the item from another app?

[ChristianTrolleMikkelsen]

We only use the web interface and the chrome extension and there we cannot see any attachments.

[kspearrin]

Fixed in 1.7.4 coming out soon. Thanks.