Closed appy-one closed 2 years ago
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"
changes
mutations
?timestamp=undefined
Fix published in v1.15.0
appy-one
commented
2 years ago
While testing I came accross this error because the methods call the
changes/mutationsendpoints on the server with?timestamp=undefinedon the server. The server doesn't accept that and returns the error "timestamp is not a number"