We're sorry AsposeCloud doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.cloud

Aspose Cloud Dropbox Storage. Access Token Expiration

I connected my dropbox as a cloud storage and it will periodically tell me that my access token will expire. I will have to go in to the settings in Aspose and regenerate a token. is there anyway to get a round this?

Thank you for contacting support.

Could you please describe step by step how to reproduce the problem you are experiencing?

every time i don’t run the program for about 4+ hours it does that. Then i go into my storage and then just click on generate then save and it works. Here is the error it gives

`    HTTP response headers: HTTPHeaderDict({'Date': 'Thu, 08 Sep 2022 02:26:40 GMT', 'Content-    Type': 'application/json; charset=utf-8', 'Content-Length': '230', 'Connection': 'keep-alive', 'Server':` 'Kestrel', 'Strict-Transport-Security': 'max-age=2592000'})
    HTTP response body: DropBox Storage exception: expired_access_token/.

and here is what i see on my end in aspose as well
image.png (59.3 KB)

Thank you for the additional information. I’ve added a ticket with ID SLIDESCLOUD-1564 to our issue tracking system. We apologize for any inconvenience. Our development team will investigate the case. You will be notified when the issue is resolved.

Thank you so much you guys are so helpful and respond so quick.

any help please very very frustrating

Our developers are working on the issue and contacted Dropbox support. It looks like Dropbox changed their token expiration policy some time ago. Unfortunately, we do not promise a quick solution to the problem.

I solved this problem on a application I had using their api recently . happy to share insight if you’d like

Please let us know, we will appreciate it.

any solution to this yet

As far as I can see, the issue has been planned to be fixed in Aspose.Slides Cloud 22.10. This version will be published in November.

any update on this? I haven’t seen any noticeable changes.

We are sorry, but the issue cannot be resolved any time soon. We expect version 23.9 to contain a fix.