Bjørn Damstedt Rasmussen
Bjørn Damstedt Rasmussen
We'll update the dependencies manually. Then we're more in control if things break.
This is where it stores channel-IDs: https://github.com/BearWare/TeamTalk5/blob/master/Library/TeamTalkLib/bin/ttsrv/ServerXML.cpp#L1322 It should store channel-path instead. If you change it then make sure to write support for the modification in ServerXML::UpdateFile: https://github.com/BearWare/TeamTalk5/blob/master/Library/TeamTalkLib/bin/ttsrv/ServerXML.cpp#L1322
When a channel is deleted then you need to sweep through the user accounts and remove the channel from all the user accounts. Only save the new xml-file if changes...
I've submitted a new TeamTalk for Android (v5.15.2). Can you check if the IPv6 issue has been fixed by some miracle?
Finally TeamTalk v5.15.2 was approved by Google Play. @jeremyp3 can you check if IPv6 is working.
I only have a Samsung Galaxy A10, which does not support IPv6, so I cannot reproduce the problem.
Send an Android phone with IPv6 support to @BearWare/contributors
hm, it's also not working on my PC. I'm suspecting it's due to a change in PortAudio. I'm suspecting the PAWIN_USE_DIRECTSOUNDFULLDUPLEXCREATE flag which switches to DirectX v8 features. It sounds...
@poretsky Any idea what could cause this error? Could it be because MainActivity's call to: ``` public void setTextMessages(Vector msgs) { messages = msgs; } ``` .. that changes TextMessageAdapter.getCount()
@beqabeqa473 do you have an idea why we're getting this error?