UUID of 0 for new entry when scripting

[troy256]

I’m encountering an issue where the lpass add command occasionally assigns a UUID of 0 to a newly created entry, and this UUID never updates to a non-zero value. This issue is causing my script, which retrieves the UUID after creating an entry, to break.

This problem seems to occur randomly after a number of entries have been successfully created. I’ve implemented several measures to mitigate this, including using the --sync=now option, incorporating sleep intervals between lpass CLI calls, and implementing a loop (with a 10-second delay between iterations) on the lpass show command to allow time for a non-zero UUID to be assigned. Despite these measures, the UUID remains at 0 indefinitely for certain entries.

It’s important to note that the issue doesn’t seem to be tied to any specific entry, as the entries it occurs on are random. I’m looking for any insights or solutions to this problem. Thanks in advance for your help.