[bug] Renaming file with new subfolder.

Completed

Matthew Smith

August 05, 2019 20:37

Naming a new file with a new subfolder works great. (And is awesome.)

Renaming a file by prepending an existing subfolder also works great. (File moves as expected.)

Renaming a file by prepending a new subfolder name, however, neither renames the file nor creates the subfolder. It also causes the file to disappear from the list. (On disk, the file remains untouched.)

Opening the folder anew restores the renamed file to the list in its pre-renamed state.

 

nvUltra v28

OSX High Sierra (10.13.6)

 

0

• 

  Fletcher Penney

  August 06, 2019 01:40

  This appears to be a sandboxing issue.  The nvUltra beta is not sandboxed due to an issue with the Sparkle update mechanism.  When run with sandboxing access enabled, this works properly.

   

  I can't explain why you can create a new folder with a new file, but not when renaming a file.

   

  Stranger is that when I then turn sandboxing back off, I can still make new folders (presumably the app still has access to prior sandboxing permissions....)

  0
• 

  Derrick Boudwin

  October 16, 2019 19:07

  I also just encountered this issue with the exact same behavior described above on MacOS Catalina, haven't messed with sandboxing though.

  0
• 

  Fletcher Penney

  October 16, 2019 21:20

  Sandboxing is built into the OS -- there's not anything you can do about it.

  0

Please sign in to leave a comment.