No but it could be caused if the get_info response doesn't actually contain methods since that's one example where we call includes in the given context:
{ "result_type": "get_info", "result": { "alias": "string", "color": "hex string", "pubkey": "hex string", "network": "string", // mainnet, testnet, signet, or regtest "block_height": 1, "block_hash": "hex string", "methods": ["pay_invoice", "get_balance", "make_invoice", "lookup_invoice", "list_transactions", "get_info"], // list of supported methods for this connection } }
But that would be a weird error, why would that suddenly happen for an existing connection.