Add support for Extended OTP Code Validity for Pair

[emp3r0r7]

Hello, i wanna say first of all : thank you for you huge work !!!

I have been using the webBuilder() method of the class responsible for generating OTP codes for user pairing in my application. However, I’ve noticed that the OTP code expires and refreshes approximately every 30 seconds, making it challenging for users to complete the pairing process if they take longer than this interval.

On the official web version of the platform, the OTP code remains valid for several minutes, allowing users to pair successfully even after a delay. This provides a smoother user experience, especially when network delays or user response times come into play.

Would it be possible to implement a feature that allows the OTP code to remain valid for a longer duration without automatically refreshing? This would help maintain a more consistent user experience similar to the official web version.

Thank you for considering this feature request.

Best regards

[emp3r0r7]

I finally managed myself to extend the OTP time duration by reverse engineering the original process from WA.
It is required to send an initial ping containing the id coming from the "pair-device" iq response.
After that, I noticed that it is required to start pinging constantly, but I may be wrong I added schedulePing() that starts pinging to emulate the original WA behavior.

Just edit the digestIq method into the StreamHandler class as follows , this solution works for me on Cobalt 0.0.6 :

 private void digestIq(Node node) {
        var container = node.findNode().orElse(null);
        if (container == null) {
            return;
        }

        switch (container.description()) {
            case "pair-device" -> {

                //patch BEGIN extended OTP
                var attributes = Attributes.of()
                        .put("id", node.id())
                        .put("type", "result")
                        .put("to", JidServer.WHATSAPP.toJid())
                        .toMap();

                var request = Node.of("iq", attributes);
                socketHandler.sendNode(request, null);
                schedulePing()
                //patch END extended OTP

                startPairing(node, container);
            }
            case "pair-success" -> confirmPairing(node, container);
        }
    }

Hope it helps, let me know if this works for you all.

[pcvarma-sayukth]

Hi emp3r0r7
Thanks for the patch. I too have same requirement.
I have tested your patch, it is working fine.

Looks like it extended the OTP indefinitely. We must extend to a certain timeout 3 minutes or so.
How to configure the OTP extension timeout? Please advise.