Originally created by @SirVaskis on GitHub (Jan 13, 2025).
What was the Problem?
Title:
Android App Appends Old Server Address to New Server Address
Description:
When updating the server address in the Android app, the new server entry gets concatenated with the old server address. This results in an invalid URL and prevents the app from connecting to the new server.
Steps to Reproduce:
Initial Setup:
Configure the app to use the old server address: http://22.22.111.11:1111
Server Change:
Delete the old server entry from the Android app.
Enter the new server address, for example: http://11.111.111.22:1111/
Result:
Attempting to connect leads to the error:
Failed to contact server. (ERROR Failed to connect server http://11.111.111.22:1111/22.22.111.11:1111)
Notice that the old server address (22.22.111.11:1111) is appended to the new one.
Expected Behavior:
The app should use only the new server address (http://11.111.111.22:1111/) for connections and completely disregard any previously stored old server address after it is deleted.
Actual Behavior:
Even after deleting the old server address, the app appends it to the new server address, causing a malformed URL and connection failure.
Troubleshooting Steps Already Taken:
Uninstalled and reinstalled the app.
Cleared the cache on the device.
Verified that the issue persists despite these steps.
Additional Notes:
The error seems to indicate that some persistent configuration is not properly cleared when the server is updated.
Steps to Reproduce the Issue
Initial Setup:
Configure the app to use the old server address: http://22.22.111.11:1111
Server Change:
Delete the old server entry from the Android app.
Enter the new server address, for example: http://11.111.111.22:1111/
Result:
Attempting to connect leads to the error:
Failed to contact server. (ERROR Failed to connect server http://11.111.111.22:1111/22.22.111.11:1111)
Notice that the old server address (22.22.111.11:1111) is appended to the new one.
What was Expected?
Expected Behavior:
The app should use only the new server address (http://11.111.111.22:1111/) for connections and completely disregard any previously stored old server address after it is deleted.
Phone Model
Ulefone Power Armor 16 pro 2022
Phone OS
Andriod 12
Audiobookshelf App Version
Android App - 0.9.77
Installation Source
Google Play Store
Additional Notes
No response
Originally created by @SirVaskis on GitHub (Jan 13, 2025).
### What was the Problem?
---
**Title:**
Android App Appends Old Server Address to New Server Address
**Description:**
When updating the server address in the Android app, the new server entry gets concatenated with the old server address. This results in an invalid URL and prevents the app from connecting to the new server.
**Steps to Reproduce:**
1. **Initial Setup:**
- Configure the app to use the old server address:
`http://22.22.111.11:1111`
2. **Server Change:**
- Delete the old server entry from the Android app.
- Enter the new server address, for example:
`http://11.111.111.22:1111/`
3. **Result:**
- Attempting to connect leads to the error:
```
Failed to contact server. (ERROR Failed to connect server http://11.111.111.22:1111/22.22.111.11:1111)
```
- Notice that the old server address (`22.22.111.11:1111`) is appended to the new one.
**Expected Behavior:**
The app should use only the new server address (`http://11.111.111.22:1111/`) for connections and completely disregard any previously stored old server address after it is deleted.
**Actual Behavior:**
Even after deleting the old server address, the app appends it to the new server address, causing a malformed URL and connection failure.
**Troubleshooting Steps Already Taken:**
- Uninstalled and reinstalled the app.
- Cleared the cache on the device.
- Verified that the issue persists despite these steps.
**Additional Notes:**
- The error seems to indicate that some persistent configuration is not properly cleared when the server is updated.
### Steps to Reproduce the Issue
1. **Initial Setup:**
- Configure the app to use the old server address:
`http://22.22.111.11:1111`
2. **Server Change:**
- Delete the old server entry from the Android app.
- Enter the new server address, for example:
`http://11.111.111.22:1111/`
3. **Result:**
- Attempting to connect leads to the error:
```
Failed to contact server. (ERROR Failed to connect server http://11.111.111.22:1111/22.22.111.11:1111)
```
- Notice that the old server address (`22.22.111.11:1111`) is appended to the new one.
### What was Expected?
**Expected Behavior:**
The app should use only the new server address (`http://11.111.111.22:1111/`) for connections and completely disregard any previously stored old server address after it is deleted.
### Phone Model
Ulefone Power Armor 16 pro 2022
### Phone OS
Andriod 12
### Audiobookshelf App Version
Android App - 0.9.77
### Installation Source
Google Play Store
### Additional Notes
_No response_
adam
added the bug label 2026-04-24 23:49:16 +02:00
I'm not able to reproduce this and can't see anywhere in the code that it is using anything except what is entered as the address.
Initial Setup:
Configure the app to use the old server address: http://22.22.111.11:1111
Does this mean you are connecting to that old server address including entering a username/password successfully?\
Server Change:
Delete the old server entry from the Android app.
Enter the new server address, for example: http://11.111.111.22:1111/
Instead of deleting the old server entry have you tested creating a new entry to see if it connects?
Are you able to connect at all with your new server address?
@advplyr commented on GitHub (Jan 13, 2025):
I'm not able to reproduce this and can't see anywhere in the code that it is using anything except what is entered as the address.
> **Initial Setup:**
>
> * Configure the app to use the old server address:
> `http://22.22.111.11:1111`
Does this mean you are connecting to that old server address including entering a username/password successfully?\
> **Server Change:**
>
> * Delete the old server entry from the Android app.
> * Enter the new server address, for example:
> `http://11.111.111.22:1111/`
Instead of deleting the old server entry have you tested creating a new entry to see if it connects?
Are you able to connect at all with your new server address?
@SirVaskis commented on GitHub (Jan 14, 2025):
Yeah this is only happening on my daughter's phone. It doesn't happen on my
phone which is strange but here's a screenshot.
On Mon, Jan 13, 2025, 21:20 advplyr ***@***.***> wrote:
> I'm not able to reproduce this and can't see anywhere in the code that it
> is using anything except what is entered as the address.
>
> *Initial Setup:*
>
> - Configure the app to use the old server address:
> http://22.22.111.11:1111
>
> Does this mean you are connecting to that old server address including
> entering a username/password successfully?\
>
> *Server Change:*
>
> - Delete the old server entry from the Android app.
> - Enter the new server address, for example:
> http://11.111.111.22:1111/
>
> Instead of deleting the old server entry have you tested creating a new
> entry to see if it connects?
>
> Are you able to connect at all with your new server address?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/advplyr/audiobookshelf-app/issues/1434#issuecomment-2588114511>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ALUK5PQV4XQIR7ZJWOMWAF32KQNZDAVCNFSM6AAAAABVCYGC5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBYGEYTINJRGE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
on her phone I cant connect to the server. I have tried creating a new ser
Instead of deleting the old server entry have you tested creating a new
entry to see if it connects? yes same issue.
Are you able to connect at all with your new server address? on my phone
yes without any issues.
[image: image.png]
On Tue, 14 Jan 2025 at 11:04, advplyr @.***> wrote:
I'm not seeing a picture. Can you respond to the other questions?
@SirVaskis commented on GitHub (Jan 15, 2025):
on her phone I cant connect to the server. I have tried creating a new ser
Instead of deleting the old server entry have you tested creating a new
entry to see if it connects? yes same issue.
Are you able to connect at all with your new server address? on my phone
yes without any issues.
[image: image.png]
On Tue, 14 Jan 2025 at 11:04, advplyr ***@***.***> wrote:
> I'm not seeing a picture. Can you respond to the other questions?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/advplyr/audiobookshelf-app/issues/1434#issuecomment-2589495201>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ALUK5PRIRXFJYLG62JJYDYL2KTOJ5AVCNFSM6AAAAABVCYGC5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBZGQ4TKMRQGE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
It seems that you have to use Github to share the picture instead of replying through email because the image is not attaching to the post.
@advplyr commented on GitHub (Jan 15, 2025):
It seems that you have to use Github to share the picture instead of replying through email because the image is not attaching to the post.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @SirVaskis on GitHub (Jan 13, 2025).
What was the Problem?
Title:
Android App Appends Old Server Address to New Server Address
Description:
When updating the server address in the Android app, the new server entry gets concatenated with the old server address. This results in an invalid URL and prevents the app from connecting to the new server.
Steps to Reproduce:
Initial Setup:
http://22.22.111.11:1111Server Change:
http://11.111.111.22:1111/Result:
22.22.111.11:1111) is appended to the new one.Expected Behavior:
The app should use only the new server address (
http://11.111.111.22:1111/) for connections and completely disregard any previously stored old server address after it is deleted.Actual Behavior:
Even after deleting the old server address, the app appends it to the new server address, causing a malformed URL and connection failure.
Troubleshooting Steps Already Taken:
Additional Notes:
Steps to Reproduce the Issue
Initial Setup:
http://22.22.111.11:1111Server Change:
http://11.111.111.22:1111/Result:
22.22.111.11:1111) is appended to the new one.What was Expected?
Expected Behavior:
The app should use only the new server address (
http://11.111.111.22:1111/) for connections and completely disregard any previously stored old server address after it is deleted.Phone Model
Ulefone Power Armor 16 pro 2022
Phone OS
Andriod 12
Audiobookshelf App Version
Android App - 0.9.77
Installation Source
Google Play Store
Additional Notes
No response
@advplyr commented on GitHub (Jan 13, 2025):
I'm not able to reproduce this and can't see anywhere in the code that it is using anything except what is entered as the address.
Does this mean you are connecting to that old server address including entering a username/password successfully?\
Instead of deleting the old server entry have you tested creating a new entry to see if it connects?
Are you able to connect at all with your new server address?
@SirVaskis commented on GitHub (Jan 14, 2025):
Yeah this is only happening on my daughter's phone. It doesn't happen on my
phone which is strange but here's a screenshot.
On Mon, Jan 13, 2025, 21:20 advplyr @.***> wrote:
@advplyr commented on GitHub (Jan 14, 2025):
I'm not seeing a picture. Can you respond to the other questions?
@SirVaskis commented on GitHub (Jan 15, 2025):
on her phone I cant connect to the server. I have tried creating a new ser
Instead of deleting the old server entry have you tested creating a new
entry to see if it connects? yes same issue.
Are you able to connect at all with your new server address? on my phone
yes without any issues.
[image: image.png]
On Tue, 14 Jan 2025 at 11:04, advplyr @.***> wrote:
@advplyr commented on GitHub (Jan 15, 2025):
It seems that you have to use Github to share the picture instead of replying through email because the image is not attaching to the post.