Frequent Appear Download did fail: BAManifestDownload Error Domain=NSURLErrorDomain Code=-999 "cancelled"

Question

Created Dec ’22

Replies 3

Boosts 0

Views 1.1k

Participants 4

Frequent Appear Download did fail: BAManifestDownload Error Domain=NSURLErrorDomain Code=-999 "cancelled" , How to resolve this error ?

Here is Logs:

Dec 30 11:16:02 backgroundassets.user[288] <Error>: Failed to send -[BADownloaderExtensionProxy sendAuthenticationChallenge:download:completionHandler:]_block_invoke for: com.xx.BADemoserror: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service with pid 1999 named com.xx.BADemos.extension was invalidated from this process." UserInfo={NSDebugDescription=The connection to service with pid 1999 named com.xx.BADemos.extension was invalidated from this process.}
Dec 30 11:16:02 backgroundassets.user[288] <Error>: Cannot message extension for 'com.xx.BADemos' to answer auth challenge, canceling challenge for download: BAManifestDownload (0xd5e839fc0) - com.xx.BADemos.Manifest-B57DC493-0E76-49A0-9429-BB40B439DC22
Dec 30 11:16:02 backgroundassets.user(CFNetwork)[288] <Notice>: Task <19F9FE6C-0DDE-419A-95F4-B309166FBA71>.<1> auth completion disp=2 cred=0x0
Dec 30 11:16:02 backgroundassets.user[288] <Notice>: Extension invalidated for identifier: com.xx.BADemos
Dec 30 11:16:02 runningboardd(RunningBoard)[31] <Notice>: Invalidating assertion 31-288-23055 (target:[xpcservice<com.xx.BADemos.extension([osservice<com.apple.backgroundassets.user>:288])>:1999]) from originator [osservice<com.apple.backgroundassets.user>:288]
Dec 30 11:16:02 backgroundassets.user(CFNetwork)[288] <Notice>: Connection 85: cleaning up
Dec 30 11:16:02 backgroundassets.user(CFNetwork)[288] <Notice>: Connection 85: summary for unused connection {protocol="h2", domain_lookup_duration_ms=0, connect_duration_ms=0, secure_connection_duration_ms=0, private_relay=false, idle_duration_ms=0}
Dec 30 11:16:03 backgroundassets.user(CFNetwork)[288] <Notice>: Task <19F9FE6C-0DDE-419A-95F4-B309166FBA71>.<1> finished with error [-999] Error Domain=NSURLErrorDomain Code=-999 UserInfo={NSErrorFailingURLStringKey=<private>, NSErrorFailingURLKey=<private>, _NSURLErrorRelatedURLSessionTaskErrorKey=<private>, _NSURLErrorFailingURLSessionTaskErrorKey=<private>, NSLocalizedDescription=<private>}
Dec 30 11:16:03 backgroundassets.user(Network)[288] <Notice>: [C85 DEA8B25F-4296-4950-8F8B-5DFBD7D54FFE Hostname#138f72b3:443 tcp, bundle id: com.xx.BADemos, url hash: 03f00812, tls, attribution: developer] cancel
Dec 30 11:16:03 backgroundassets.user(Network)[288] <Notice>: [C85 Hostname#138f72b3:443 tcp, bundle id: com.xx.BADemos, url hash: 03f00812, tls, attribution: developer] cancelled
Dec 30 11:16:03 backgroundassets.user[288] <Error>: Download did fail: BAManifestDownload (0xd5e839fc0) - com.xx.BADemos.Manifest-B57DC493-0E76-49A0-9429-BB40B439DC22 with error: Error Domain=NSURLErrorDomain Code=-999 "cancelled" UserInfo={NSErrorFailingURLStringKey=https://xx.xx.com/321809_7fb0d3cb44918c0c3598ae15d151713d.json, NSErrorFailingURLKey=https://https://xx.xx.com/321809_7fb0d3cb44918c0c3598ae15d151713d.json321809_7fb0d3cb44918c0c3598ae15d151713d.json, _NSURLErrorRelatedURLSessionTaskErrorKey=(
    "LocalDownloadTask <19F9FE6C-0DDE-419A-95F4-B309166FBA71>.<1>"
), _NSURLErrorFailingURLSessionTaskErrorKey=LocalDownloadTask <19F9FE6C-0DDE-419A-95F4-B309166FBA71>.<1>, NSLocalizedDescription=cancelled}

Boost

Answer 1

Systems Engineer OP

Apple

Jan ’23

It looks to me like your App Extension is crashing when the system asks it to respond to the authentication challenge protocol listed in BADownloaderExtension. I'd recommend attaching to the extension to see what is causing the crash.

1

Answer 2

Fourth OP

Mar ’23

Have you figured it out?I'm struggling with it. I managed to attack to the extension, and it always triggers backgroundDownload:failedWithError with the same error info like you.

0

Answer 3

josh_yan OP

Aug ’23

Have you tried to add

if (@available(iOS 16.1, *)) {
        [BADownloadManager sharedManager];
}

I met the same problem, and found that add this when app launched can fix this problem.

0