OsmAnd Track Upload Fails: Auth Issue On Dev Server

Hey everyone, I've run into a bit of a snag while trying to upload a recorded track from the OsmAnd~ Android app, and I'm hoping you guys can lend a hand. It seems like the app is attempting to authenticate against the development server instead of the production one, leading to a failed authentication. Let's dive into the details, the steps to reproduce the issue, and what's going on with the environment setup. I am using the OsmAnd application to record my tracks, and I usually upload them to my account so I can review them later or share them with my friends. Recently, I've had issues when trying to upload the tracks I recorded; the application requests authorization on the wrong server, and I cannot log in. This has become very frustrating, so I decided to seek help from the community. Let's see what we can do.

The Problem: Authentication on the Wrong Server

So, here's the deal. After recording a track using the OsmAnd~ Android app, I went to upload it to my account. When the app tried to authenticate, it was pointing towards the development server: https://master.apis.dev.openstreetmap.org/login? Now, this is a problem because, well, it's the dev server. My account and all the production stuff live on the real, live server. Naturally, the authentication failed. It's like trying to use a key that doesn't fit the lock, you know? This prevents me from uploading my tracks and defeats the whole purpose of using the feature. This is really frustrating and I hope we can find a solution together. The app should be pointing to the production server so I can upload all my recorded tracks. The fact that the authentication is being directed to the development server is the core of the problem, and understanding how this is happening is essential for a fix. I have searched online for a solution but I have not found anyone facing the same issue. I hope this helps to troubleshoot and find a solution.

Let's break down the steps to reproduce the issue, so we can all get on the same page and figure out what's going wrong. I need to make sure that the recorded tracks are uploaded to the correct place, so I can keep on using the application.

Steps to Reproduce the Issue: A Step-by-Step Guide

Okay, so here's exactly what I did, step by step, to run into this authentication issue. Following these steps should allow anyone to reproduce the problem and hopefully pinpoint the cause. This should help to understand the context and maybe replicate it. I hope you find this helpful and can help me with this problem. I have already tried to reinstall the application, but it did not work, so I am open to suggestions. I will gladly try any solution provided.

1. Record a Track: First things first, I fired up the OsmAnd~ Android app and started recording a track. I went for a walk around the neighborhood, making sure the GPS was happily tracking my movements. This step is pretty standard; nothing unusual here. The recording itself worked as expected; the app captured all the necessary data, such as GPS coordinates and timestamps. No issues encountered during this phase. I just started the recording and let it do its job. It was running perfectly.
2. Attempt to Upload: Once the walk was over and I had a nice track recorded, I tapped the upload button. This is where things started to go sideways. I was expecting the usual upload process, where the app would securely send my track data to my account on the production server. This process had always worked fine before, so I did not expect any issues.
3. Authentication Attempt: Instead of the smooth upload, the app tried to authenticate against the development server: https://master.apis.dev.openstreetmap.org/login? This is where the red flag went up. I knew this wasn't right because I have never used the dev server. I expected the app to communicate with the production server, where my account and track data are hosted.
4. Authentication Failure: As a result of the incorrect server address, the authentication attempt failed. I wasn't able to log in, and the track upload didn't proceed. The app displayed an error message, informing me that the authentication had failed. This was a clear indication of a problem with the server address.

So, that's the whole shebang. Pretty straightforward, right? Now, let's look at what's supposed to happen.

Expected Result: Smooth Upload to the Production Server

What I'd expect to happen, and what should be happening, is a seamless upload of my recorded track to the production server. This means:

• Authentication on the Production Server: The app should be connecting to the correct server, which is the live, production server, for authentication. The URL should point to the correct endpoint where my account resides.
• Successful Login: After authenticating, I should be able to log in successfully using my credentials. The app should verify my account details against the production server database.
• Track Upload: Once logged in, the app should upload the recorded track data without any issues. The track data should be securely transferred to my account on the production server.
• Confirmation: Finally, I should receive confirmation that the track has been successfully uploaded. The app should provide feedback, such as a success message, and allow me to view the uploaded track. I should be able to see the uploaded tracks on my profile.

That's the ideal scenario, and it's what I've experienced in the past. Unfortunately, that's not what's happening now. So, let's explore my environment to see if we can identify any clues.

My Environment: The Tech Specs

To help you guys troubleshoot, here's the technical environment I'm using. It might give us some clues about what's going on. This information is crucial for pinpointing the cause of the problem. If it is a common issue with the version, it would be easy to find a workaround. Knowing the specific versions and configurations is essential.

• OsmAnd Version: 5.1.9: This is the specific version of the OsmAnd app I'm using. It is important to know if there is a known issue on the version I have. If so, a workaround or an update may be available.
• Android version: 15: I'm running Android 15. The compatibility of the application with the operating system may be a factor. I keep my system updated to get the best out of the applications I use. The compatibility between the app and the operating system version should be considered.
• Device model: Poco F3 on LineageOS: I'm using a Poco F3, with LineageOS. I've tried reinstalling the application and restarting my phone, but the issue persists. This is the hardware and software configuration. It's good to know the specific device model and the custom ROM. This may help in identifying any compatibility issues.

With this information in hand, hopefully, we can get to the bottom of this. Let me know if you need any more details! I'm ready to provide any additional info or run tests to help resolve this issue. If anyone has seen this before or has any ideas, please chime in! All suggestions are welcome; the more eyes we have on this, the better. We can use this information to analyze potential causes and solutions. Let's work together to figure out what's causing the app to authenticate against the development server instead of the production one and get my track uploads working again. Looking forward to hearing your thoughts and solutions! I hope to have the uploading feature working as soon as possible. Thanks in advance for your time and effort! We will find a solution together.