You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Widget works well, when i type some message to the project I see it in firebase database.
Unfortunately, after login to dashboard there is nothing in request. When I click chat, I'm logged well, and see my id like in firebase, but no one message is delivered.
I really don't know how to find soultion for this problem. Which applications made this problem. There is no error in console, when I use chat21-ionic.
It's also strange that I see on chat21-ionic's list other users, created by tiledesk-dashboard and i can chat with them(fist person in chat21-ionic gui, second too). In this way it works, but why it doesn't works with widget?
Hi
Will you please help me I am unable to see user in ionic app
I am able to get messages in dashboard "request" tab but when I click on "open chat"
Ionic page is loaded with "no conversation yet"
Hello.
I'm trying to run your application. I started 4 services by Docker:
https://github.com/Tiledesk/tiledesk-server
https://github.com/Tiledesk/tiledesk-dashboard
https://github.com/chat21/chat21-web-widget
https://github.com/chat21/chat21-ionic
Widget works well, when i type some message to the project I see it in firebase database.
Unfortunately, after login to dashboard there is nothing in request. When I click chat, I'm logged well, and see my id like in firebase, but no one message is delivered.
I really don't know how to find soultion for this problem. Which applications made this problem. There is no error in console, when I use chat21-ionic.
I deployed functions to firebase:
https://ibb.co/J2Y18cC
It's also strange that I see on chat21-ionic's list other users, created by tiledesk-dashboard and i can chat with them(fist person in chat21-ionic gui, second too). In this way it works, but why it doesn't works with widget?
Database works like this:
https://ibb.co/19L09tH
The text was updated successfully, but these errors were encountered: