Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Illegal folder name can’t be fixed in any imaginable way (probably need to remove the app and reconfigure it from scratch) #3203

Open
gianks opened this issue Nov 20, 2024 · 1 comment

Comments

@gianks
Copy link

gianks commented Nov 20, 2024

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. Create a folder with invalid chars in it on IOS app
  2. You are stuck in a loop, the app will keep attempting to sync forever, failing every few seconds
  3. You can’t delete or rename the folder, the first either local or local/remote will produce no effect, rename will give back an insufficient permission issue

Expected behaviour

The app prevents to create such illegal folder, quits attempting to sync it continuously (as the error message wrongfully states), allow to delete it locally and/or remove it to amend the pending sync.

Actual behaviour

Allows the illegal name and goes crazy about it…

Logs

If applicable, you can post the iOS app or server logs (removing any sensitive information).

Reasoning or why should it be changed/implemented?

Environment data

iOS version: e.g. iOS 17.6.1

Nextcloud iOS app version: see More > Settings

Server operating system:

Web server: Apache, nginx

Database:

PHP version:

Nextcloud version: see Nextcloud admin page

@looowizz
Copy link

Hi, I just experienced the same issue and it seems you can stop the pop up by going to More > Transfers and cancelling the folder creation transfer.

Kinda surprised this hasn’t been fixed yet as it should just be a simple if statement when editing the folder name, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants