Open MAISTA23 opened 6 years ago
same issue
whatsapp probably changed something in how it work
same issue: Message dropped because the port is closed Signed in but not recording
Same issue
Have you guys found any solution or good alternative?
It still works fo me without an issue. Running windows 10
@ga-mer Yeah they probably did something to their systems, but not all at once worldwide, so maybe somewhere this amazing stool is still up and running.
Anyone here good at this code? The record seems to still recognize online users. It just wont report to online/timeline. There should be a workaround. I tried a bit but failed ;D
I have workaround for this problem.. Will post as soon as I get home.
On Mon 16 Apr, 2018, 6:23 PM MAISTA23, notifications@github.com wrote:
Anyone here good at this code? The record seems to still recognize online users. It just wont report to online/timeline. There should be a workaround. I tried a bit but failed ;D
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/andrey-leshenko/WaTracker/issues/14#issuecomment-381588732, or mute the thread https://github.com/notifications/unsubscribe-auth/AQfQ0j9znOfI8ZThSTZK37ZutWRwGI_Sks5tpJROgaJpZM4TRuII .
I have workaround for this problem.. Will post as soon as I get home.
Nice ;)
Awesome great job
I guess due to some server side changes in web whatsapp, the 'wa_stream_start' message type never occurs, instead we see a 'wa_logged_in' message. So I have modified the code in record.js file to accommodate the changes. Do note that this fix is in no way a permanent solution and may need a better solution after studying all the changes that have occurred in web whatsapp.
Attached record.js file, replace the one in the folder by this and reload the extension in chrome. Will send a pull request once I get the time to make some enhancements to this awesome tracker.
btw the app still works despite the warning in the readme file about google dropping support for chrome apps
was this canned?
I guess due to some server side changes in web whatsapp, the 'wa_stream_start' message type never occurs, instead we see a 'wa_logged_in' message. So I have modified the code in record.js file to accommodate the changes. Do note that this fix is in no way a permanent solution and may need a better solution after studying all the changes that have occurred in web whatsapp.
Attached record.js file, replace the one in the folder by this and reload the extension in chrome. Will send a pull request once I get the time to make some enhancements to this awesome tracker.
record.zip
Thanks alot. Do you have any workaround for the tracker only recording contacts with an active conversation tab? writing something and not sending it doesnt work for me NVM, got it. You have to click the contacts once to get recognized
Wow WaTracker is back! Thanks a lot for that
WOW !!! Not even is it working again, you also fixed the stream_end error, so you had to restart.
@kedaranmol you are fucking awesome
Doesnt work. 'Message dropped because the port is closed' Ubuntu linux chrome
I had to insert lines
if (!port) port = chrome.runtime.connect({name: 'presenceUpdates'});
in record.js in line 58
And it works ))
NVM, got it. You have to click the contacts once to get recognized
That's not working for me. After a few minutes it doesn't recognize online activities as long as you don't have an open conversation with the contact or, at least, open the empty chat on smartphone and laptop.
Any solution for that? Did WhatsApp change things here?
On 2nd may whatsapp changed something. no tracking software is working right now
Worked fine yesterday. Today only this :
Theres at least one other user with the same problem. What happened?