-
Notifications
You must be signed in to change notification settings - Fork 806
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
sendTextMessage no errors, but doing nothing, not sending the message #177
Comments
What is the response you get back from the python server? |
Hey, attached you will find the console output: Sending message from the phone to the number in question "manually" on the phone itself:
Print when I hit my "send" button. All the parameters are entirely copied from the "logout" button (except that the command is
Error I sometimes get after sending. First line might be a print I've added to the code:
|
Check out arunrreddy/whatsapp-web-reveng. I have made a few changes to make it work. |
@arunrreddy thank you but unfortunately this can't connect for me.
JS console:
Python console
With the index.html.
|
I am not sure of the demo but the actual implementation works fine. i.e the
server running on localhost:2018
…On Mon, Mar 25, 2019, 9:58 PM tulssinep ***@***.***> wrote:
@arunrreddy <https://github.com/arunrreddy> thank you but unfortunately
this can't connect for me.
Click to connect to API
Connecting to API
Connection to API closed. Click to reconnect
JS console:
whatsapp-web-reveng jsdemo server listening on port 2021
Python console
[2] Sass is watching for changes. Press Ctrl-C to stop.
[2]
[1] [nodemon] 1.18.3
[0] [nodemon] 1.18.3
[0] [nodemon] to restart at any time, enter `rs`
[1] [nodemon] to restart at any time, enter `rs`
[1] [nodemon] watching: *.*
[0] [nodemon] watching: *.*
[1] [nodemon] starting `python2.7 ./backend/whatsapp_web_backend.py`
[0] [nodemon] starting `node index.js`
[0] whatsapp-web-reveng API server listening on port 2019
[0] Creating new connection 0
[0] whatsapp-web-reveng HTTP server listening on port 2018
[1] whatsapp-web-backend listening on port 2020
With the index.html.
login-via-js-demo.html loads the QR code just fine but on the index.html
nothing happens. Anything I need to configure?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#177 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQ_9XBi0hy0eLOVUljDzah94g2FVdVrmks5vaPlDgaJpZM4cAlkJ>
.
|
Hey, just tried it, I'm getting the exact same on Tried with both Chrome and Safari, taken straight from this repo here runs fine, yours does not :( Because my paths are messed up a bit, I've had to hardcode |
I have configured a sendmessage button on the ui itself. I have hard-coded the number though. Did you try that? |
Sorry I don't understand the question; I put the number at |
Ah, I cloned the repo. Installed python requirements using pip and node
requirements using npm and then ran npm run dev. This worked like a charm.
…On Tue, Mar 26, 2019, 12:17 AM tulssinep ***@***.***> wrote:
Sorry if I didn't explain correctly; I can't get there because of the API
connection loop on your repo;
[image: ware2fork-api-error4]
<https://user-images.githubusercontent.com/11710965/54945679-b0875c00-4f36-11e9-8460-66616c97573a.gif>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#177 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQ_9XNwQQpkgRh9l28jCgyEfliJgqR3sks5vaRmsgaJpZM4cAlkJ>
.
|
hi, may i know do u solve the problem of wrong timestamp when sent a message out ? |
Hey i tried everything I could. The go-whatsapp library doesn't have this
issue. It has something to do with the encryption and decryption I guess. I
tried to reverse engineer the go library but wasn't able to do it.
…On Tue, Mar 26, 2019, 5:21 PM kelvin5290 ***@***.***> wrote:
Check out arunrreddy/whatsapp-web-reveng. I have made a few changes to
make it work.
hi, may i know do u solve the problem of wrong timestamp when sent a
message out ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#177 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQ_9XEGg-prc_ffWX8QQ0zLzN6piGWiYks5vagnWgaJpZM4cAlkJ>
.
|
i tried using the decryption script to decrypt the encripted message, it seem no problem. |
Can you share the script? I might find something. Also the user list which
WhatsApp sends back has only nine digits apart from the country code? Do
you have any idea why this is happening?
…On Tue, Mar 26, 2019, 5:34 PM kelvin5290 ***@***.***> wrote:
i tried using the decryption script to decrypt the encripted message, it
seem no problem.
I stuck in here for few month and maybe the problem is coming from python
coding.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#177 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQ_9XHcniH21vXJrEIhm4mkBKXv7JGSqks5vagyygaJpZM4cAlkJ>
.
|
@tulssinep hai, can I have take a look to your works if you still have it? |
I've logged in, messages on group chats etc. makes them appear in the the console. Good.
I've duplicated the disconnect button from the JS HTML interface, renamed it and made it call a test method that eventually calls
currWhatsAppInstance.sendTextMessage("55xxxxxx@c.us","Test");
I've had to do a ton of imports and the method eventually ran through without breaking the process, everything good - except for the fact that the message doesn't get sent. I've tried with different phone numbers etc. the message simply won't appear in the conversation on either device. I've deleted the conversation to make sure it's not buried on the wrong timestamp but no change.
The sendTextMessage does get called, I put text file writes in it and they all get written.
Any idea what I'm doing wrong? Did I miss something?
The text was updated successfully, but these errors were encountered: