Rollup of builds 212-219 since v1.0-build211. Two things matter here: newly
created calls dying on you, and the captcha screen refusing every answer.
NEW: Get VK call URL (Settings › VK Call Link)
Around 3 August VK changed how calls end. A call you create by hand in a
browser now dies the moment you leave it, so a link made today stops working
almost immediately and the app says "Call not found". Links made before that
change are unaffected, which is why this hit new setups hardest.
A call created through VK's API does not die — it stays usable with nobody in
it. The new button does exactly that: it confirms which VK account to use,
creates the call, and puts the new link at the top of the VK Call Link field,
keeping whatever was already there. The next connection uses it.
It is not anonymous, and the screen says so before anything happens: the call
belongs to the VK account you confirm, so a burner account is the sensible
choice. If you have already used "Use VK account (cookie) auth", the saved
login is reused and there is nothing more to fill in.
Thanks to @Molniya-Game for pointing at calls.start, to @stranger11rus for
working out what VK had actually changed and for the "connect before you
leave the call" workaround that kept people going in the meantime, and to
@FearMuchGg and @assketick for the reports and testing that pinned it down.
FIXES
The captcha inside the app was rejected no matter what you did — even a real
human tap on "I'm not a robot" came back as if a robot had done it. The app
was telling VK it was Safari 17.0 while actually running your phone's current
Safari, and VK's own script, running inside that browser, could see the
difference.
Now that one tap is enough again, and it does more than get you past that
screen: the app learns from the accepted attempt and then passes on its own.
Measured after the fix, a single tap kept it going unattended for more than
nine hours with no further prompting.
The Connect button now greys out when something required is missing. It used
to stay blue and simply ignore the tap, which looked like the app was broken
rather than like a field above needed filling in.
Also: the diagnostic "Force legacy captcha path" switch in Settings › Advanced
now works from the main app too, and survives an export/import round trip. It
is a troubleshooting aid — leave it off unless asked to turn it on.