What you provided is not a URL. Both of those are invalid.
I try again, I think the forum software deleted some parts. Maybe a typo, it's hot here, concentration is suffering.
Before (valid): https://www.our-server.com/api.php?pass=USER-PASSWORD
After (invalid): https://www.our-server.com/api.php=USER-PASSWORD
I checked the logs, the user is offline again but I can not confirm the URL changed. The app is not sending at all, I can't see valid or invalid URLs in the log, it must have something to do with the app. The user sent me screenshots, settings are ok, wifi is ok, GPS is ok. We have problems over problems since the app received the recent update, it worked many years, now it's all breaking apart and people complain they are not tracked or going offline for no reason.
Traccar Client doesn't change any URLs by itself. Only user can change it.
Have you updated your server to handle the new payload format?
Yes, it's working perfectly fine with JSON. Other users are online, so we know it's working. However, this user promised he didn't change anything. After we managed to fix his URL settings back to valid, we received some API calls, now he is offline again but nobody knows why.
Overall result of the app update is that it cut activity on our map in half. Not all users report problems or call for support, they just leave in frustration. I have statistics for project wide tracking activity and I can confirm that we lost a lot of users. Typically there is very high activity with severe storms approaching, I have never seen so few storm chasers on our map. It matches with the app update. I really loved Traccar but right now, there are problems and tracking seems to be broken or dead for many users. Those who are online also look strange. Fewer data points, very big gaps.
Have you read other threads? There are changes to the configuration options, but there is a way to make it works the same way as before.
Can you guide us to specific threads or app documentation? There are tons of threads regarding problems, it's hard to find the right solutions.
For example this:
Today, I received a report that the app changed the server URL without any user input. We received 1 successful API call, then it changed to an invalid URL.
Before (valid):
our-server.com/api?pass=USER-PASSWORD
After (invalid):
our-server.com/api=USER-PASSWORD
Even after changing the URL back to valid, the app fired invalid URLs. Finally, after about 1 hour, the changed URL finally came back to life.
Is there any possibility this could be a rare and undetected bug?
Update: As I'm writing this, the user is offline again, the URL has been changed to invalid without any user interaction (user is driving right now and not interacting with his device at all). For me, that's the confirmation it must be a bug.