Merge branch 'fix-contact-sync'
* fix-contact-sync:
Contact sync needs to happen when we discover a new gateway
Skip contact sync work if there are no gateways configured
Merge branch 'master' of github.com:iNPUTmice/Conversations
* 'master' of github.com:iNPUTmice/Conversations:
bump agp
version bump to 2.10.6
pulled translations from transifex
do not merge failed decryptions
version bump firebasse-messaging lib
Contact sync needs to happen when we discover a new gateway
Since that can change the outcome of the sync operation.
Skip contact sync work if there are no gateways configured
Or if syncing before gateways have been discovered, etc. Don't do the work if
we know nothing will come of it.
Merge branch 'darker'
* darker:
Darker Obsidian
Merge branch '3GPP-video'
* 3GPP-video:
Move video MIME above audio MIME
Move video MIME above audio MIME
So that when a file extension is ambiguous, we guess video.
pulled translations from transifex
do not merge failed decryptions
fixes #4314
Merge branch 'master' of github.com:iNPUTmice/Conversations
* 'master' of github.com:iNPUTmice/Conversations:
pulled translations from transifex
Revert "flush stanzas in batches"
fix NPE during bookmark creation
bump agp
null check axolotl service when getting trust
check domain name against DNSName to avoid rare crashes
work around platform bug when getting restrict background
pulled translations from transifex
Call setActive anyway in CONNECTED state
There is no code that guarantees the state must go through CONNECTING
before being CONNECTED. To avoid potential bugs, call setActive anyway
here.
Add @RequiresApi annotation for dialer integration
to stop the linter complaining every second line of code
Use StatusHint label to signal connecting state
set in-call UI active in the connecting state
Currently, if the "CONNECTING" stage of a Jingle call takes a
significant amount of time (say, a second), then there will be a window
where the call is already accepted but the ringing UI is still showing.
This 1) is confusing; 2) allows the user to accept a call twice, which
will cause a crash.
Unfortunately, there is no native equivalent to the "CONNECTING" state.
The only sane choice here seems to be showing the in-call UI even if the
call is still connecting.