For some reason, it does not populate the database with the streams

[mattjaf]

New Bug Report

https://github.com/MoralisWeb3/Moralis-JS-SDK/tree/main/demos/parse-server-migration

Issue Description

For some reason, it does not populate the database with the streams, while authentication does.

and the documentation is different than the video, the URL is appended with /streams while in the repo its streams-webhook?

Steps + code to reproduce

1. clone the repo
2. setup mongo db cluster and redis
3. deploy a contract
4. setup a stream with the moralis admin dashboard
5. trigger an event
6. check the ngrok tunnel and database for a response

Actual Outcome

When I trigger an event I can see it in the moralis admin dashboard, while I don't get a response in the DB nor in the ngrok tunnel.

Expected Outcome

for it to work like it did in the video...

Environment

Server

• Moralis server version: 2.11.1

Client

• Moralis SDK version: 2.11.1
• Operating system: windows 11
• Browser: chrome

Logs

i do not get a 200 ok in my ngrok tunnel as shown in the video

[mattjaf]

there's /streams-webhook everywhere and the part that seems to matter is,

app.use(
  streamsSync(parseServer, {
    apiKey: config.MORALIS_API_KEY,
    webhookUrl: '/streams',
  }),
);

...yall gotta stop changing the names of things

I also, clicked the production slider and it seemed to fix it

[mattjaf]

it seems like this is what they wanted it to be

app.use(
  streamsSync(parseServer, {
    apiKey: config.MORALIS_API_KEY,
    webhookUrl: config.STREAMS_WEBHOOK_URL,
  }),
);

Imo, why not just leave it as /streams??? why type out an extra -webhook no point in breaking the video and the demo/prod slider shouldn't prevent pushing to the database...

i literally watched that video like 20 times and this seriously almost made me cry

please fix this

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. for your contributions. If this issue is still affecting you, please leave any comment, and we'll keep it open We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! Thank you.

[stale[bot]]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!