how to deal with V2 groups

[piramiday]

after my update to 0.7.0 I tried playing around with a test V2 group.
this was a bad idea, I guess, since the Signal server now has seen that my bot supports groups V2 and decided to upgrade all my groups to V2 (!) ...
the bot is invited to each V2 group by default, but cannot accept the invitation!

what's the proper way to proceed? continuing from #354.

I have:

1. reset my profile using updateProfile
2. sent myself a direct message
3. received new messages
4. invoked updateAccount

still nothing -- listGroups shows all my groups V2 as inactive!
any help is appreciated. thanks!

[piramiday]

I've removed my bot from all groups (manually) and reinvited it (manually) and now there was no invitation limbo, the bot just appeared in the chat.
I'll leave this issue open for a few days to help others, but anybody using signal-cli v0.7.0 might try out updating the profile as a first thing, and who knows, maybe the system will work alright in that case.

[piramiday]

I guess the remaining functionalities were added in https://github.com/AsamK/signal-cli/releases/tag/v0.7.1 ... 👍