Runtime Error / doesn't connect anymore

[kurokirasama]

Hello,

I'm having issues connecting. I got this screen for a while:

Then it changes to this, and it remains there forever:

Also, 2 out of 5 times I run the app I got this screen:

Regards,

[Saliba-san]

same here!

[johnwuelk]

same here, fails on different devices.

[bbbart]

yes, that's happening here as well

[normen]

Yeah, I guess its time to finish up the whatsmeow version, I didn't (and probably still won't for some time) find much time to complete that though.

[sozoalvin]

does anybody have a clue on where to start debugging? i can help to take a look

[normen]

For those that want to help fix this, check out the whatsmeow branch, it should work logging in and retrieving messages (when using multiclient). The main remaining thing is storing all needed info of a message (ID?) in the local DB so one can later recreate message objects in a form the whatsmeow library understands (e.g. to retrieve additional info like images, to quote etc.).

[kurokirasama]

@normen whatsmeow branch gives me this error when building with go build:

build github.com/normen/whatscli: cannot load embed: malformed module path "embed": missing dot in first path element

[normen]

Just use the makefile, something seems to be off there, I don't get this issue. Maybe run a make get before.

[kurokirasama]

like this?

make get Makefile

I got the same error, maybe I'm missing some go dependencies...

go get
build github.com/normen/whatscli: cannot load embed: malformed module path "embed": missing dot in first path element
make: *** [Makefile:16: get] Error 1

[normen]

Try pulling again, I pushed my local changes, its all WIP mind you!

[kurokirasama]

I might be doing something wrong because I got the same error, is make get Makefile correct?

[normen]

make get would be the command but the added Makefile doesn't really change anything I guess. No idea whats going wrong there for you.

[kurokirasama]

@normen it was a version problem. I had installed 1.13, it was necessary 1.18

[TheSashmo]

Is this issue closed or still open? I can't use the application either, I get the same message as the post lists, 1.11 is the latest release, but I see comments for 1.13 and 1.18.

[normen]

Is this issue closed or still open? I can't use the application either, I get the same message as the post lists, 1.11 is the latest release, but I see comments for 1.13 and 1.18.

In my browser its still open. kurokirasama is talking about the golang version for compiling the WIP branch.

[b3h3m0th]

Right, so what you are saying is one should start debugging on the whatsmeow branch and the releases are basically broken?

[normen]

Seems to depend on the region and settings if its still working. The whatsmeow branch needs to be finished, not debugged.

[ZobairQ]

im having the same problem

[CPbt4uaub2arkpX8sY2LApxIiSqkD9VP]

I'm still having this issue

[icrescenti]

No solution it seems

[CPbt4uaub2arkpX8sY2LApxIiSqkD9VP]

Indeex

On Sat, Aug 13, 2022, 15:18 icrescenti @.***> wrote:

No solution it seems

— Reply to this email directly, view it on GitHub https://github.com/normen/whatscli/issues/72#issuecomment-1213897104, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVEGAZMEBJT6PZMQSEMUZPLVY5D37ANCNFSM5TLMCO4A . You are receiving this because you commented.Message ID: @.***>

[CPbt4uaub2arkpX8sY2LApxIiSqkD9VP]

I had an older install of whatscli and a ubuntu PC, even that did not work, this means it is a change on whatsapp's end that denies our connection. I doubt we can go anywhere from here unless we can see what this one thing is. I might look at similar projects and see how we can employ some of the methodologies used in said other projects. Despite all that I repeat my point that we might not go anywhere from here.

[normen]

Again, the solution is the new whatsmeow library for which a branch of whatscli exists but isn't finished.

[CPbt4uaub2arkpX8sY2LApxIiSqkD9VP]

Thanks, I'll check it out.

On Tue, Aug 16, 2022, 18:06 Normen Hansen @.***> wrote:

Again, the solution is the new whatsmeow library for which a branch of whatscli exists but isn't finished.

— Reply to this email directly, view it on GitHub https://github.com/normen/whatscli/issues/72#issuecomment-1216431430, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVEGAZKZNXU2SQ2YMPQVWA3VZNR3ZANCNFSM5TLMCO4A . You are receiving this because you commented.Message ID: @.***>

[michalspano]

Still interested about this.

[CPbt4uaub2arkpX8sY2LApxIiSqkD9VP]

Yes, I'm still interested.

On Mon, Sep 26, 2022, 19:39 Michal Špano @.***> wrote:

Still interested about this.

— Reply to this email directly, view it on GitHub https://github.com/normen/whatscli/issues/72#issuecomment-1257899994, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVEGAZOQD6UIJLIJ6QGJSO3WAGDOLANCNFSM5TLMCO4A . You are receiving this because you commented.Message ID: @.***>

[slarrain]

Hopefully the whatsmeow branch picks up some pace. WhatsApp, unfortunately, is incredibly important to so many millions of people that it deserves a proper CLI/TUI client.

[normen]

I'm still swamped in other code and projects. But it's in the back of my mind.

Having looked at the whatsmeow library a bit more, by now I think boiling down the whole codebase to a simple whatsmeow frontend without any abstractions is probably the better way to go.

[slarrain]

Thanks @normen . I'd wish this project was done on Python, so I could help you out and you wouldn't have to be the sole developer of this project. Unfortunately, No GO for me.

By the way, if you want us to try different branches and versions, just ping us. Good luck with whatsmeow!

[martin-braun]

@normen If my understanding is correct, the whatsmeow branch is working, but crippled. I respect that there are times where you cannot work on this, this is FOSS and anybody can pickup your work at anytime. However, I think it would be useful to have rather a limited experience than no experience, so how about making an update on Homebrew nonetheless?