Prompts to select folder as security scoped bookmark cannot be created

[sebsto]

Hello,

Since I upgraded to macOS Sequoia, Cyberduck 9.0.2 shows 4 file selection dialogs when starting the app, before I can access the S3 browser view. After that, it works as usual. It will repeatedly show this File open dialog every time I start the app.

See attached animated gif as an example.

Is this a bug ? Is there a workaround ?

[sebsto]

Link to Gif : https://github.com/user-attachments/assets/55747c55-27ee-452d-8783-5d33fa557668

[tatze96]

Do you use the App Store version of Cyberduck?

Can you please enable debug logging, recreate the issue, and send us the log file afterward? If you don't like to see sensitive data to be shared publicly, please send the log file with the ticket reference GH-16367 to support@cyberduck.io, otherwise attach it here.

Sidenote: If you want to share the log file here, make sure to attach it through the GitHub web interface, as it wouldn't be visible to us otherwise.

[Xjs]

I observed the same behaviour and sent a debug log to you, seems to have ended up in your internal ticket CD-12944. Be sure to correlate that one to this issue if you wish to investigate further.

[sebsto]

Same problem occurred again today. I don't why it appears and until when it will interrupt my workflow :-(. I reopened this issue.

[sebsto]

@tatze96

Do you use the App Store version of Cyberduck
yes

After a reboot of macOS, I cannot reproduce anymore.

Closing this for now

[sebsto]

Problem happened again. I'm re-opening this and I sent my logs files by email (your references CD-12954 and CD-12955)

[dkocher]

The prompt is shown ¹ because we fail to obtain a security scoped bookmark for the folder location when running in a sandbox (installed from the Mac App Store). This might be related to a regression in macOS 15 ².

Footnotes

1. f98beb4 ↩

2. https://forums.developer.apple.com/forums/thread/764435?answerId=806097022#806097022 ↩

[dkocher]

I cannot seem to reproduce the issue myself.

[sebsto]

Thank you for the investigation.
from the thread on Apple forums, it appears this will be corrected on macOS 15.1, correct ?