Skip to content
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

The status of my connections is always "OPENING" #654

Open
pedro-severo opened this issue Aug 26, 2024 · 2 comments
Open

The status of my connections is always "OPENING" #654

pedro-severo opened this issue Aug 26, 2024 · 2 comments

Comments

@pedro-severo
Copy link

pedro-severo commented Aug 26, 2024

Hey there!

On my first steps with the project, I'm facing an issue with the connections that I create using the UI interface:

image


All connections that I create still with this look, as the connection is loading before to be able to connect some whatsapp number using the qrcode button:

image


After a quick debug, I saw that these connections created on UI are always saved as status "OPENING" in database, no matter which value is on the code. Even if I set the default value of the status properties as another value, as I did on the print bellow, setting default as "qrcode", on the database the value of status is always saved as OPENING.

image


I'm assuming this fact ("on the database the value of status is always saved as OPENING"), because, after my change above, the log of the connection object saved on database shows the status prop as "qrcode", until the last moment before the calling of the method who handle with database saving. But, when I get this saved object again, using the get's endpoints, the object comes with status prop as "OPENING" since the first moment after the object comes from database. The result is that print above, who shows the connection whit a look of loading:

image

In resume, for some reason, the status as "OPENING" of my connections never changes, what makes impossible to connect whatsapp numbers for my connections.

Someone knows how to solve it?

@CJRMedeiros123
Copy link

CJRMedeiros123 commented Aug 27, 2024

Hello! Check the google chrome version.

I was same problem, and when i change for Google Chrome 126.0.6478.182-1 back work again.
image

The code is
sudo apt-get update
sudo apt-get install libappindicator1
sudo dpkg -i google-chrome-stable_current_amd64.deb

@pedro-severo
Copy link
Author

Hi @CJRMedeiros123!

Thanks by your support.

I'm not using apt-get and dpkg commands directly on terminal, because I'm using a mac. But change to 26.0.6478.182-1 version in Dockerfile didn't work for me. This is my image now:

RUN apt-get update \
    && apt-get install -y wget gnupg \
    && wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - \
    && sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' \
    && apt-get update \
    && wget https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_126.0.6478.182-1_amd64.deb \
    && apt-get install -y \
        ./google-chrome-stable_126.0.6478.182-1_amd64.deb \
        libappindicator1 fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst fonts-freefont-ttf libxss1 \
        --no-install-recommends \
    && rm -rf /var/lib/apt/lists/* \
    && rm google-chrome-stable_126.0.6478.182-1_amd64.deb

Changes:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants
@pedro-severo @CJRMedeiros123 and others