-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with social-messenger-ts #74
Comments
hi @matsmello, thanks for trying out our demo. From the screenshot you provided, everything seems to be ok as the error you see shouldn't be related to us but to some 3rd party browser extension you might be using. The probable reason why your version of the app looks empty is the lack of data. May I ask you to create a few users and channels in our backend dashboard first? Additionally, you can use the following sample data generator (useful for test/dev environments): Please let me know how it goes. |
Hello @oliverlaz, thank you for the quick response. This is my current dashboard: I can see conversations and users on the dashboard but on the react app I am still seeing this: Can you tell me if it is working on your side? I don't want to bother you for something stupid on my side. |
hi @matsmello, can you check whether your current user You can read more about filtering and querying in general in our documentation: |
Hello team, I tried to run the social-messenger-ts repository but unfortunately didn't work.
I added the variable keys to the
.env
file but this was my final result.I am also receiving this error on my console tab on Google Chrome.
These were my steps:
yarn install
.env-example
to.env.development
To find the
REACT_APP_STREAM_KEY
, I used this value:To find the
REACT_APP_USER_ID
, I used this value:To find the
REACT_APP_USER_TOKEN
, I used the link mentioned with the secret and user id mentioned above.Probably, I am missing something since it is my first time using this service, but I would appreciate some help, thank you in advance.
The text was updated successfully, but these errors were encountered: