lingochamp / lingochamp/FileDownloader

总是提示FileDownloader.DownloadServiceNotConnectedHelper: request get the status for the task[-1820460891] in the download service, but the download service isn't connected yet.

Open
#1,361 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
11.1k
Forks
2.2k
PR merge metrics
No merged PRs in 30d

Description

![image](https://user-images.githubusercontent.com/21138025/95844338-64e80d80-0d7b-11eb-9aac-1037636088f2.png)
一直弹出这个弹窗,并且会打印下面的错误信息,我已经调用了bindService
I/BufferQueueProducer: [SurfaceTexture-1-31736-7](this:0xc2f7f000,id:7,api:4,p:659,c:31736) queueBuffer: slot 3 is dropped, handle=0xc96ee000
2020-10-12 19:03:22.949 31736-31736/com.sathio.com W/FileDownloader.DownloadServiceNotConnectedHelper: request get the status for the task[-1820460891] in the download service, but the download service isn't connected yet.
You can use FileDownloader#isServiceConnected() to check whether the service has been connected,
besides you can use following functions easier to control your code invoke after the service has been connected:
1. FileDownloader#bindService(Runnable)
2. FileDownloader#insureServiceBind()
3. FileDownloader#insureServiceBindAsync()

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported FileDownloader.DownloadServiceNotConnectedHelper warning and the FileDownloader#bindService, #isServiceConnected, #insureServiceBind, and #insureServiceBindAsync entry points. Reproduce the task-status request around service binding and determine the lifecycle or timing that causes the warning; done means the reported popup and warning no longer occur in the demonstrated scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.