Eugene Voloshchak

Not overdue, PR was merged recently

Not overdue, PR has been deployed to production 5 days ago

I agree with @joelbettner on [this](https://github.com/Expensify/App/issues/15996#issuecomment-1484973151) > I think the scope of fixing this should be fixing the entire track distance selector and not just the error that we get...

This isn't isolated to two different requests, it can also happen with one request being called twice (or more). This issue can be reproduced even when you quickly change only...

@khatch33's [proposal](https://github.com/Expensify/App/issues/15996#issuecomment-1486202310) is more detailed, and explains **why** this error occurs. The root cause of this is indeed `lastModified` value. If you make a second request while the first one...

@ShogunFire's [proposal](https://github.com/Expensify/App/issues/15996#issuecomment-1487763981): > I propose that we only have one call to the API to modify the rate and the unit and that this method be called when we click...

@khatch33 > waiting for a response before sending another request is what I was alluding to. However I think even with that, it would be more intuitive to combine both...

@podrascanindragan47, thanks for the updated [proposal](https://github.com/Expensify/App/issues/15996#issuecomment-1486048909)! Btw, it's better to post a new one instead of editing the previous comment. Your proposal is disabling the ability to edit while another...

@podrascanindragan47, thanks for the updated proposal! We already have a network queue in https://github.com/Expensify/App/tree/main/src/libs/Network that you can make use of. However, it seems like this can be reproduced using two...

I was able to reproduce this on v1.2.94-3 from the AppStore