I see the same but why this happen also with Offline buffering: off and why the client than uses such a old outdated timestamp
To me it sounds like it got stuck on uploading some previous position and it takes a long time for whatever reason.
When I first observed this behavior, my initial assumption was that the client-side queue might be filled or blocked for some reason.
To test this, I disabled offline buffering and restarted the iPhone. While I was not certain whether this would fully clear any existing queue, I wanted to rule it out as a potential cause. However, the behavior remained unchanged.
I then deleted the app entirely and reinstalled it, under the assumption that this would remove all locally stored data and reset any internal queues. Despite this, the issue persisted and the behavior did not change after reinstallation.
I tested the setup against a newly created server, and the “Busy with previous request” issue does not occur there.
The testing is not yet complete and has so far only been done using “send position”. However, even with this limited test, the UI updated immediately, unlike on the old server where outdated timestamps were still shown. This suggests that the issue may be server-related.
What I find unusual is that an Android device with identical settings worked correctly on the old server.
I will continue testing tomorrow and may also try some optimizations or adjustments on the MySQL database.
I see a lot of this:
Which indicates that some other request is already in progress.