Skip to content

Conversation

@Gabrielx47
Copy link

I'm having trouble running the WhatsApp application:
Screenshot from 2026-01-28 16-48-48

I used npm audit fix, but that didn't solve the problem.

I'm also having problems with the whatsapp-web.js package.
Screenshot from 2026-01-25 08-09-46

This problem occurs when a message is sent and the bot attempts to read it. The current version of the whatsapp-web.js package is 1.34.2. However, even after updating to version 1.34.4, the problem persists.

Copy link
Owner

@mcruzdev mcruzdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for this pull request @Gabrielx47, it looks great and will help more people to try it locally!

I left few comments, could you update our documentation that talks how to run locally?

<artifactId>quarkus-quinoa</artifactId>
<version>${quarkus-quinoa.version}</version>
</dependency>
<dependency>
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's keep both

Copy link
Author

@Gabrielx47 Gabrielx47 Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay. Both are necessary, as one is used for local execution and the other for production execution.

whatsapp.incoming-message.queue-url=${INCOMING_MESSAGE_FIFO_URL}
whatsapp.recognized-message.queue-url=${RECOGNIZED_MESSAGE_FIFO_URL}

%local.quarkus.http.auth.proactive=false
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why we need this one?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why we need this one?

This is necessary because, for the registration to be successful, without it the server returns a 401 error. I still don't understand why, since the SignUpResource class has the @PermitAll annotation. In theory, the server shouldn't deny the registration. From what I've researched, this happens due to Quarkus' proactive authentication.
Screenshot from 2026-01-30 07-16-02

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This error occurs because it's in a pull request that has already been fixed #195

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This error occurs because it's in a pull request that has already been fixed #195

Good morning, @matheusandre1! I did a merge between the main branch and my branch.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you remove this file from changes?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.

@Gabrielx47
Copy link
Author

Gabrielx47 commented Jan 30, 2026

Thanks a lot for this pull request @Gabrielx47, it looks great and will help more people to try it locally!

I left few comments, could you update our documentation that talks how to run locally?

Good morning, @mcruzdev! I'm happy to contribute and gain knowledge at the same time. I'll update the documentation.

@mcruzdev
Copy link
Owner

Thanks a lot for this pull request @Gabrielx47, it looks great and will help more people to try it locally!
I left few comments, could you update our documentation that talks how to run locally?

Good morning, @mcruzdev! I'm happy to contribute and gain knowledge at the same time. I'll update the documentation.

Sounds good friend! You are welcome :)

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

Successfully merging this pull request may close these issues.

3 participants