Registration Error: 31409, Conflict

[domenic39]

Im not sure if this is OS specific, but I currently only have seen this error on Android.

I have a callback for Voice Event Errors

this.voice.addListener(Voice.Event.Error, this.handleVoiceError);

  private readonly handleVoiceError = (error: TwilioError) => {
    console.log('Voice error detected', error);
  };

I see the following log in production. It is unclear to me what is the cause or repercussions of this error. Any details are greatly appreciated.

Voice error detected {"message":"Conflict (31409): Conflict","name":"Conflict","stack":"Conflict: Conflict (31409): Conflict\n at construct (native)\n at apply (native)\n at _construct (address at index.android.bundle:1:168019)\n at Wrapper (address at index.android.bundle:1:167673)\n at construct (native)\n at _callSuper (address at index.android.bundle:1:2469573)\n at TwilioError (address at index.android.bundle:1:2469795)\n at construct (native)\n at _callSuper (address at index.android.bundle:1:2472038)\n at Conflict (address at index.android.bundle:1:2478174)\n at constructTwilioError (address at index.android.bundle:1:2470111)\n at anonymous (address at index.android.bundle:1:2455049)\n at anonymous (address at index.android.bundle:1:2454735)\n at apply (native)\n at emit (address at index.android.bundle:1:203657)\n at apply (native)\n at anonymous (address at index.android.bundle:1:202046)\n at emit (address at index.android.bundle:1:202340)","causes":[],"description":"Conflict (HTTP)","explanation":"The request could not be processed because of a conflict in the current state of the resource. Another request may be in progress.","solutions":[],"code":31409}

[mhuynh5757]

@domenic39 when do you see this issue occur? Is it when you make a call or register your device?

[domenic39]

I am fairly certain it happens during device registration

My running theory is I have a bug in my code where I trigger device registration multiple times, would this error correlate to that scenario?

[mhuynh5757]

That could be the case. You can check Android logcat to validate, or just put a log where you invoke voice.register. That error code is straight from the Twilio backend, and given that it's referring to an in-use resource, your hypothesis is sound.

You can also await voice.register since it's an async method that directly correlates to the native registration code.