Skip to content
Back

RealtimeResponseEvent Typescript Bug

  • 0
  • Web
  • Realtime
  • Cloud
Rostlino
26 Jan, 2026, 22:09

Hello, could you please fix RealtimeResposneEvent, the one in realtime.ts have timestamp: string, but the one in client.ts have timestamp: number, and it causes issues like

import { type RealtimeResponseEvent } from 'appwrite';

await new Realtime(client).subscribe(['lorem', 'ipsum'], (event: RealtimeResponseEvent<T>) => { console.log(event.payload); });

Types of property **timestamp **are incompatible. Type string is not assignable to type number

TL;DR
Issue: RealtimeResponseEvent has conflicting types (string vs number) for timestamp in files realtime.ts and client.ts, causing TypeScript mismatch error. Solution: Determine the correct type for your use case (string or number) and ensure consistency across both files to resolve the conflict.
Joshua
26 Jan, 2026, 22:36

I can help! The issue is caused by a type mismatch RealtimeResponseEvent has timestamp: string in realtime.ts but timestamp: number in client.ts, creating a conflict when TypeScript tries to reconcile them. Which file has the correct type for your use case - should timestamp be a string or a number?

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more