Android: crash when trying to call a ringID with all RING accounts dissabled
Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)
If all RING accounts are dissabled, entering a new RingID and trying to call it or calling an already used RingID will cause the application to crash. I don't have the logs, but with Adrien we saw it was a nullptr issue due to trying to make a call with a dissabled account. Seems like its an issue possibly on both the client and daemon side, as the client shouldn't try to make a call with a dissabled account and neither should the daemon.