cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Share your feedback on the Document Scanning Experience in the Dropbox App right here.

Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Re: Download works on iPhone but not on iPad

Download works on iPhone but not on iPad

Sk8St4r
Helpful | Level 5
Go to solution

Got weird behaviour when downloading file. Everything works as expected on iPhone but when building for iPad download "hangs". As I do not really get a response I cannot give the error message.

 

 

 

[[client.filesRoutes downloadData:fromPathStr]
     response:^(DBFILESFileMetadata *result, DBFILESDownloadError *routeError, DBRequestError *error, NSData *fileData) {
         NSLog(@"Reached on iPhone but not on iPad");   
     }];

 

 

just updated pods to last version of ObjectiveDropboxOfficial (3.0.15)...probem persists

1 Accepted Solution

Accepted Solutions

Sk8St4r
Helpful | Level 5
Go to solution

Q: "To clarify though, are you saying that code execution never progresses past the downloadData call, or that the response block is never called?"

A: The response block was never called.

 

Seems like pod was not updating correctly. Deleted and installed again. Now i am on 3.1.0 and after reconstructing linking process and renaming types everything seems to work now!

 

Thanks for the hint.

 

View solution in original post

2 Replies 2

Greg-DB
Dropbox Staff
Go to solution
The latest release is actually 3.1.0, not 3.0.15. Please update to that, as there have been some fixes that may be relevant here. (Also, are you sure you updated to 3.0.15? The 'response' method was renamed to 'setResponseBlock' in 3.0.0.)

If the issue persists with 3.1.0, we can look into this with you. To clarify though, are you saying that code execution never progresses past the downloadData call, or that the response block is never called? (The actual network call and response block occur asynchronously.)

Sk8St4r
Helpful | Level 5
Go to solution

Q: "To clarify though, are you saying that code execution never progresses past the downloadData call, or that the response block is never called?"

A: The response block was never called.

 

Seems like pod was not updating correctly. Deleted and installed again. Now i am on 3.1.0 and after reconstructing linking process and renaming types everything seems to work now!

 

Thanks for the hint.

 

Need more support?