-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DBDownloadUrlTask permission issue 513 under iOS 10.3 #125
Comments
|
@Sipeso: Thanks for reaching out. I'm looking into the issue now! |
|
@Sipeso silly question but is your app setup for App Groups under Capabilities? You need to assign it the same container Id that you have specified there. It won't work, I think, otherwise. I had the same issue but I'm not experiencing anything since my app uses App Groups on both the Mac and iOS. |
|
@Sipeso can you also try with |
|
@guidedways: Thanks for the helpful suggestions. I'm still struggling to understand why this would be a 513 permissions issue. When you experienced this issue, did you experience it when building for multiple device-types on the same simulator? Did you ever experience this on a physical device? @Sipeso: When you experience this issue was it on a physical device or on the simulator? Do you experience the same issue on iOS 10.3/iPad Pro 12.9 after going to Simulator > Reset Content and Settings...? |
|
@scobbe I actually never tested it on a simulator - I've learned never to really trust the simulator so all my tests were on real devices (an iPhone 10.3 and iPad 10.0) - so I can confirm I was seeing this on both 10.0 and 10.3 |
|
@scobbe for what it's worth, I don't understand why it fails for some and why it doesn't for others.. plus the 513 error doesn't make sense. Most certainly a NSURLSession bug (given v1 didn't use NSURLSession and v2 does - and we never saw these in v1). I've just recently ported from v1 to v2 and started seeing this immediately. Devices still using v1 did not. |
|
@guidedways: Thanks for the perspective! This is helpful. |
|
Dear all, Now it works on all physically used devices and iOS installation (as mentioned above) with the following DBClientsManager configuration: In our case it definitely does not work under iOS 10.3/iPad Pro 12.9" when forceForegroundSession is set to 'NO'. @quidedways: Under the Capabilities 'App Groups' are switched off, we don't need it. Fyi: Our latest app store version runs still the Dropbox API v1 (Core API). That is why we are currently migrating to v2 and preparing the app for the next app store release. So, thank you very much again for all your help. |
|
@Sipeso that's great! Yeah I suspect background |
|
@guidedways Thank you very much for your great support for solving our issue and your advice concerning the checkAndPerformV1TokenMigration (what we are implementing right now). |
|
I have same problem with iOS 10.3 on iPhone and Dropbox SDK (last version). I set forceForegroundSession to YES but no result... sometimes I have no error... but more frequently my download fails... and error is criptic... |
|
@alebaldi: I think I might have determined with the issue is. Please try updating to the latest version of the SDK, v3.0.18, and see if that fixes your issue. |
|
@scobbe with last version, 3.0.18, it's all ok. I have three App, and all Apps now it's all ok. Thank you very much! ;-) |
|
@scobbe i am also facing same issue. |
|
@shoaibhassanWhizpool It sounds like you may be running in to a somewhat different issue. The issue reported here was for a specific error, but you said you're not getting anything. Please open a new issue with the details of the issue you're seeing (i.e., steps to reproduce the issue, relevant code, etc.). Thanks |
After setting the responseBlock on the following download task:
I am getting the error message:
It works for us on iPad with iOS 9.3.5/iPad2 and iOS 10.2/iPad Air 2 but it fails on an iOS 10.3/iPad Pro 12.9". This morning I made a pod update to version 3.0.10 but this has not resolved the problem.
I also followed the proposals from the issue: #60 with the following implementation:
But the problem still exists.
Thank you very much in advance for your great support and for suggestions…
The text was updated successfully, but these errors were encountered: