Downloads don't progress past enqueued.

[DeanPack]

I'm trying to download files from my webserver, there is required authorization, so I'm sending an authorization header, like so

    task.taskId = await FlutterDownloader.enqueue(
      url: task.link!,
      headers: {'authorization': '[Bearer ${store.state.auth.accessToken}]'},
      savedDir: _localPath,
      saveInPublicStorage: true,
    );

I have my background isolate running and getting updates, but it just gets the queued update, and nothing else, despite however long I wait.

To reproduce the bug, Just try to download a file and have your background isolate watching. I imagine this might have something to do with authorization, but if that is the case, I would expect some kind of error reporting so I'm not just shooting in the dark like I currently am.

Expected behavior

I expect the download to start from the queue instead of just sitting there with the queued status indefinitely.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Device information:

Iphone SE 3rd generation 16.0 emulator

Additional context

[brunoda6]

Hi I have the same problem but mine only doesn’t work on iOS realese mode, have you found out the problem?

thanks

[daverin]

@brunoda6 I just hit this issue now. Trying to trace my steps back to see what triggered this.

[daverin]

#629 solved my issue.

Here's a nice explanation: firebase/flutterfire#9446 (comment)

[julianfalcionelli]

Same as for @brunoda6 , on the latest Flutter version (3.3.7) the downloads are not working in iOS Release Mode.

Update: After adding the annotation @daverin mentioned everything is working fine.

[markst]

Just tested Flutter version (3.3.7) and appears to still work without 'vm:entry-point'. Not sure when this issue was introduced.

[markst]

Update: Version 1.10.2 does seem to resolve issue for me:

[✓] Flutter (Channel beta, 3.8.0-10.1.pre, on macOS 13.0.1 22A400 darwin-arm64, locale en-AU)

[markst]

ah my issue seems to be related to: #804
whether or not @DeanPack is the same issue...