We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
OAuth permissions issues in SwiftyDropbox under Ventura?
Have there been any changes in recent versions of SwiftyDropbox to accommodate any new security restrictions on Ventura?
I developed a macOS app with a FileProvider Finder extension, which initialises smoothly under Monterey and earlier versions; however, some people installing it on Ventura are reporting a whole string of "Allow / Deny / Always Allow" dialogs repeatedly asking the user to enter the "login" keychain password to access "com.<companyname>.<appname>.dropbox.authv2". So it looks like something might have changed in Ventura's default security handling.
The app was built with SwiftyDropbox 8.2.1; I did a minor tweak to the OAuth Keychain code, to make sure it saved the tokens to a keychain related to an app group (so it can be accessed both by my main app and the extension). So I'm trying to work out whether this is a known issue related to Ventura and I should update the app to use SwiftyDropbox 9.2, or whether the issue is something I need to fix outside of SwiftyDropbox!
Update on this: I think the infinite number of Dropbox warnings were down to startup issues -- the FileProvider extension was trying to get basic Dropbox details (including the local path) before checking whether the main app was up and running yet, so it would keep reiterating the warning while the main app was still trying to authenticate. The solution was to move the initial Dropbox calls to after the main app had successfully authenticated.
We still get two access warnings on initial authentication, but we can live with that! Thanks.
Do you have any more details of the "fixes for use in application extensions"? For our limited use of Dropbox in our extension, we haven't had any problems to date under Monterey.
- Greg-DB
Dropbox Staff
You can find the release history for SwiftyDropbox here. There is a "Fixes for use in application extensions" in the latest release, v9.2.0, which might be relevant. Please try updating to that. If something still isn't working as expected with that, please share the specific steps/code to reproduce the issue so we can look into it. Thanks!
Update on this: I think the infinite number of Dropbox warnings were down to startup issues -- the FileProvider extension was trying to get basic Dropbox details (including the local path) before checking whether the main app was up and running yet, so it would keep reiterating the warning while the main app was still trying to authenticate. The solution was to move the initial Dropbox calls to after the main app had successfully authenticated.
We still get two access warnings on initial authentication, but we can live with that! Thanks.
Do you have any more details of the "fixes for use in application extensions"? For our limited use of Dropbox in our extension, we haven't had any problems to date under Monterey.
Further update: the FileProvider fix in 9.2.0 appears to be specific to iOS mobile devices -- this is a desktop macOS FileProvider, so not relevant to us.
So thanks -- this is a non-issue!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
