Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Invalid characters can be created in file names on Android

Abierto
  • ¿Algo no está bien?
#545 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
android, kotlin
Área
mobile

Línea de trabajo

El payload no menciona archivos fuente ni pruebas. Empieza por reproducir el problema con la bóveda dañada adjunta y compara los nombres con saltos de línea creados por Android a través de WebDAV con WinFsp o el montaje automático; estará terminado cuando los nombres no válidos se rechacen o la ruta de acceso afectada los gestione con un error informativo o una opción de recuperación.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

type:bug
Please agree to the following
Summary

Android client allows accidentally creating filenames with characters, that break directory access on Windows

System Setup
- Android: 
  - Android 14
  - Samsung Galaxy A52s
  - Google Play system update "November 1 2023".
  - Cryptomator: 1.10.2
- PC: 
  - Windows 11, 23H2. 
  - Cryptomator 1.13.0
  - WinFSP installed
  - Setting "Default Volume Type": "Automatic"
Cloud Type

Dropbox

Steps to Reproduce
  1. On Android, select some text containing newlines but no other characters potentially problematic as file name.
  2. "Copy" the text
  3. Use "Share > Cryptomator" on some image on a webpage.
  4. Paste the text into the file name field when uploading to a cryptomator vault.
Expected Behavior

Not completely clear:

  • Either Cryptomator on Android should reject the newline, or
  • Cryptomator on Windows should allow the newline or, if the issue is with the Windows APIs instead,
  • Translate it on Windows to something, the system can work with, or
  • Show a more informative error message, maybe a "rename file now" option.
Actual Behavior

When viewing the vault on PC,

  • The root directory is listed as usual.
  • Trying to copy the file (Ctrl+C, Ctrl+V or drag-and-drop with Ctrl held down) leads to an error Error 0x80070057: The parameter is incorrect.
    image
  • Trying to copy the file to a subdirectory will create the same error message, but on Android, the copied file is still visible.
  • Subsequently, the sub directory is shown as empty in Explorer, while the root directory remains viewable.
  • This pattern repeats with other software, e.g. in cmd, the dir command can list the root directory, including the newline character, but fails for the subdirectory with an error "File not found".
  • Similarly, using os.listdir on Android yields the list of files (including newline characters) in the root directory, but fails with an exception FileNotFoundError: [WinError 206] The filename or extension is too long: 'foo' for the subdirectory.
    image
Reproducibility

Always

Relevant Log Output
Nothing relevant to report for the log files. The last entry prior to reproducing the failing behavior is just "10:36:37.078 [JavaFX Application Thread] INFO  o.c.ui.unlock.UnlockWorkflow - Unlock of 'test bug' succeeded.", and nothing after that. Errors show up in Python, CMD "dir" and the directory is listed as empty, but nothing shows up in the log.
Anything else?

The issue is not reproducible by creating a file with newline characters directly on Windows, e.g. using Python, i.e. for the behavior to break, for some reason the file must originally have been created on Android, even though they should have the exactly same name, see screenshot below:
image

After manually changing the mount type of the vault, it looks like the issue occurs only when mounting with WebDAV. However, originally the mount type was set to "automatic" in the Cryptomator settings, and "Default (WinFsp)" in the vault settings. After testing the different mount types and setting it back to "Default (WinFsp)", the issue is now gone unless I explicitly set the vault to "WebDAV", indicating that Cryptomator may have previously used WebDAV as the default after all.

An example broken vault is attached with password helloworld:
example_broken_vault.zip
The subdirectory subdirectory_populated_by_dragndrop shows the described breakage under webdav access.

Lenguaje dominante
Kotlin
Estrellas
1.2k
Forks
216
Merge medio
1 d 20 h
PR fusionados (30 d)
9

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cryptomator/android

Todos los issues de cryptomator/android

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.