Local copy could not be renamed try a different name

help

#1

Anyone having this problem when trying to log on from Android?

Keeps saying Local Copy could not be renamed try a different name. Not sure why it keeps doing that
when trying to access from Android device. I can get to the server via web but not via app.
thanks in advance.


#2

Which server version are you using?

Version 2.9 of Android app only supports server version 9.x and newer. I encourage you to upgrade your server version, and any question or problem about it, check it here: https://central.owncloud.org/

If you don’t have the choice to upgrade your server, you can get the 2.8.0 version (the latest Android version that supports old server versions) from F-Droid. To get it, follow these steps:

  1. Install F-droid app from http://f-droid.org
  2. In F-droid app, tap on “Settings”, placed in the bottom bar.
  3. Tap on “Repositories”
  4. Enable the option “F-Droid Archive”
  5. Go back to the F-Droid main screen, and search for ownCloud by using the lens icon on the floating button
  6. Scroll down, and in “versions”, get the 2.8.0 version

Let us know any problem or suggestion you have.


#3

I’m having the same issue with the android app … i’m using server version 10.0.10.4 and app version 2.9.3
I’ve setup a DDNS name that works with a browser and the windows app. When i try the android app i get the ‘Local Copy could not be renamed try a different name’ error. also the app works if i’m connected to my home wifi and use the server ip address.

Does anyone have a solution ?
Thanks


#4

Same issue here. I don’t have access to the server, so upgrading it is not an option for me. Truth be told, I’m not even sure how to find out which server version I’m on. I did, however, successfully follow all the steps listed in jesmrec’s post and that did not solve the problem. Same error message with Android client version 2.8.0.
I’ll try johntigner’s method next to see if I can’t at least get the app to work while I’m at home. It’d be lovely if someone could actually pinpoint the actual root of the problem…
Thanks!


#5

Hey,

maybe this is a bug in the Androind App? You could try to report it to https://github.com/owncloud/android/issues then.