I tried making a comment on my keyboard app using a browser extension to see the event structure, and it seems like your implementation has missing parent item tags from NIP-22

The event generated looks like this:

{
"kind": 1111,
"tags": [
["A", "32267:573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e:in.unsigned.keyboard"],
["K", "32267"],
["P", "573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e"],
["d", "1.0.0"]
],
"content": "My comment..."
}

The tags there should look like:

"tags": [
// root scope (uppercase)
["A", "32267:573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e:in.unsigned.keyboard", "<optional-relay-url>"],
["K", "32267"],
["P", "573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e", "<optional-relay-url>"],

// parent item (lowercase - same as root for top-level comments)
["a", "32267:573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e:in.unsigned.keyboard", "<optional-relay-url>"],
["k", "32267"],
["p", "573010eb0f43fcfc253c2895828d30bf6939b056384e2cc6648f40096acaef4e", "<optional-relay-url>"]
]

I'm not sure about the added d tag, but the parent item tags are required in the NIP

Also, not sure if it was a deliberate choice for some reason, but if not, this is probably a bug