yonybe please read the 4 last pages of the thread. WhatsApp is blocking Yappari because it uses an older version of the protocol and these days they are blocking other non official clients like WhatsApp + too.
Arrives correctly msg to authenticate , but soon requests a new authentication
That's because Yappari can't understand what's going on and asks you to re-register. That's all.
The only solution is that ceene uses the coderus implementation of 1.4 (or 1.5) since the projects are very similar. Even though coderus already did most of the work, it's still A LOT of work for Yappari.
Is there the possibility that the new header parameters on v1.1.55 cause some new bad behavior after they "lift" this 24-hour ban thingie? I started getting "Reply: {"status":"fail","reason":"format_wrong"}" registration errors after updating to v1.1.55, while before they where always "bad_param"...
This is just for information's sake, I understand that the question is about using new protocol versions on Yappari, but if the "lift" comes in form of servers accepting protocol v1.2 once again (at least temporarily), wouldn't the recent changes become a burden?
...then again, it should be trivial to revert back to old behavior?.
I kinda get baffeld on these
For example pick any phone and you are able to call and sms and these im services are crazy like new phone new yet another non standerd service
That's because Yappari can't understand what's going on and asks you to re-register. That's all.
The only solution is that ceene uses the coderus implementation of 1.4 (or 1.5) since the projects are very similar. Even though coderus already did most of the work, it's still A LOT of work for Yappari.
