Closed Ahineya closed 2 years ago
This is odd. It looks like the type of req.body
in replicache-pull.ts is string
not Object
as expected. I believe Next.js detects the correct type by the content-type header sent to replicache-pull. Replicache is supposed to send Content-Type: application/json
and in my dev inspector I can see that to be the case. Do you see something different?
@aboodman Yep, no Content-Type header in my case:
What is the body payload? Also what browser is this?
Nevermind browser question, I see the user agent.
The payload is:
{"profileID":"p26c0d1259e714a49a1b59f906c3e4807","clientID":"ecf3e1f8-6839-47bf-bd1d-d5a48cb87014","cookie":null,"lastMutationID":0,"pullVersion":0,"schemaVersion":""}
Ok, weird. I tried another browser, and it works now. If I find the cause of this behavior, I will update the ticket.
Could it be an extension? I also noticed some cookies in the request body. Our sample doesn't add any cookies. Perhaps another clue.
@aboodman Yep, it was the extension. "Mokku" with a default configuration logs all requests to the localhost, and looks like breaks something.
Thanks for your help!
Hi, Went step-by-step with the https://doc.replicache.dev to set up the todo app. The app is running, but the collaboration does not work. Are there any additional steps needed to be done?