I definitely suspect coracle is feeding it something bogus, since both likes and comments work as expected (and I assume nos2x signing is completely indifferent to the event type, except as far as permission checks)
The error is coming from nos2x:
This might be nostr:nprofile1qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tcpzdmhxue69uhhwmm59e6hg7r09ehkuef0qythwumn8ghj7enjv4h8xtnwdaehgu339e3k7mf0qyd8wumn8ghj7mn0wd68ytn5dpjhxctdv43kzapwd9hj7qgcwaehxw309ahx7um5wgh8x6tydekxzcnn9ehxctcqyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze65qkltc 's problem, at least because the error message is undefined. But I wouldn't rule out coracle passing something broken to nos2x.
Discussion
nostr:nprofile1qyw8wumn8ghj76r0v3kxymmy9e3k7unpvdkx2tn5dahkcue0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcprdmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdakj7qpqjlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3q87k8ew I don't know if it changed but this is what the response from nos2x is. Why is coracle trying to use nip44 encryption to update my follow list? I do have encryption denied right now so it's correct that nos2x is denying the request.
Oh wait, that's in the nos2x client library anyway lol, so yeah I guess it's a nos2x bug?