You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Attempt to relink Dropbox? keeps recurring
I updated my iOS app to use the latest Dropbox SDK over the weekend, and initially it seemed fine. But now I notice that whenever I go someplace new and reopen my app, it says my Dropbox account is ...
This is iOS. According to the Info.plist in the Dropbox framework, it's version 3.6.2.
When the app first starts I see this, not sure if it is important:
-[NSKeyedUnarchiver validateAllowedClass:forKey:] allowed unarchiving safe plist type ''NSString' (0xxxxxxx) [/System/Library/Frameworks/Foundation.framework]' for key 'accessToken', even though it was not explicitly included in the client allowed classes set: '{(
"'DBAccessToken' (0xxxxxxx) [/var/containers/Bundle/Application/xxxxxxx/XXXXXX.app/Frameworks/ObjectiveDropboxOfficial.framework]"
)}'. This will be disallowed in the future.
Then a bit later I think from this -[Uploader(Private) connection:didReceiveData:]: self:0xxxxxxxx
getCurrentAccount returned2022-07-08 08:37:09.878568-0500 xxxxx[xxx:xxxx] DropboxAuthError[{
ErrorContent = "expired_access_token/...";
RequestId = xxxxxxxxxxxxxxxxxxxx;
StatusCode = 401;
StructuredAuthError = "<DBAUTHAuthError: 0x282311ae0>";
UserMessage = nil;
}];
Any idea why my access token would expire?
Going over the Github documentation, I suspect this is happening because I still use the long-lived token and had not switched to the V2 version...
So ... I switched to using the "newest" method with DBScopeRequest, but now it will no longer authorize even temporarily. It does not open the Dropbox app or Safari to authenticate anymore. And when I switched back to the way my code was before, it does the same thing - no longer authorizing.
Currently in my code I am checking if [[DBClientsManager authorizedClient] != nil) then I assume the app is authorized. But I guess that is no longer true? It is giving me the "expired access token" error even though DBClientsManager authorizedClient] != nil. Is that expected?
If I disregard the fact that I supposedly have an authorizedClient and I call authorizeFromControllerV2, it does open the Dropbox app and ask me to Allow, but then gives an error "An error occurred authorizing your app. Please try again." The only thing in the log at that point is "DBSDKReachability Flag Status" -R"
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
