The Dropbox-API seems to have a bug where the listContents function in DropboxAdapter:175 gets into an endless loop for some folders.
The returned entries become at some point only 1 entry which is the $location itself but the index "has_more" still is true.
This happens in our company for only one specific folder. The function and API call for other folders behaves as expected.
As this is a quite random behavior I haven't encountered anywhere else, I thought I let you know.
Maybe someone has the same problem. Maybe someone knows whats going on. Maybe its my fault. I don't know.
Any input as to how to go about it is welcome.
The Dropbox-API seems to have a bug where the listContents function in DropboxAdapter:175 gets into an endless loop for some folders.
The returned entries become at some point only 1 entry which is the $location itself but the index "has_more" still is true.
This happens in our company for only one specific folder. The function and API call for other folders behaves as expected.
As this is a quite random behavior I haven't encountered anywhere else, I thought I let you know.
Maybe someone has the same problem. Maybe someone knows whats going on. Maybe its my fault. I don't know.
Any input as to how to go about it is welcome.