Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
When doing background transfers on iOS, `DidFinishEventsForBackgroundSession` doesn't appear to ever fire. Brandon Minnick followed the below tutorial & sample app, and only `DidCompleteWithError` fires when the download completes; he even checked that `NSError==null`, which is true, which indicates that the download was successful.
The below StackOverflow link seems to collaborate his findings.
It seems that we are not alone in this boat, seems to happen also in ObjC
The above question provides some good findings:
These delegate methods won't get called if:
* The app is already running when the tasks finish;
* The app was terminated by double-tapping on the device's home button and manually killing it; or
* If you fail to start a background NSURLSession with the same identifier.
Also there are some comments that this won't work in the simulator, that it will just fire on device.
Nick do you mind testing if the above answers this? I can check later if you can't, since you guys have a workaround this is a little low priority now vs iOS 10 tasks :)
Sounds to me like Alex answered the question.
@Nick, please try again with (a) recent betas of Xamarin.iOS and (b) Xcode8 GM.
I'm closing this issue but if you're still experiencing this, feel free to re-open the bug.