[GH-ISSUE #21] Error: "timestamp is not a number" on getMutations and getChanges with cursor #16

New issue

Closed

opened 2026-05-23 08:34:22 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-23 08:34:22 -06:00

Owner

Originally created by @appy-one on GitHub (May 20, 2022).
Original GitHub issue: https://github.com/appy-one/acebase-client/issues/21

Originally assigned to: @appy-one on GitHub.

While testing I came accross this error because the methods call the changes / mutations endpoints on the server with ?timestamp=undefined on the server. The server doesn't accept that and returns the error "timestamp is not a number"

Originally created by @appy-one on GitHub (May 20, 2022). Original GitHub issue: https://github.com/appy-one/acebase-client/issues/21 Originally assigned to: @appy-one on GitHub. While testing I came accross this error because the methods call the `changes` / `mutations` endpoints on the server with `?timestamp=undefined` on the server. The server doesn't accept that and returns the error "timestamp is not a number"