lingochamp / lingochamp/FileDownloader
android15上调用FileDownloader.getImpl().bindService()的时候出现SecurityException
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 11.1k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
调用FileDownloader.getImpl().bindService()时出现以下错误：java.lang.SecurityException: Unable to start service Intent { cmp=www.test.com/com.liulishuo.filedownloader.services.FileDownloadService$SeparateProcessService (has extras) }: Unable to launch app www.test.com/10696 for service Intent { cmp=www.test.com/com.liulishuo.filedownloader.services.FileDownloadService$SeparateProcessService }: process is bad
at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1983)
at android.app.ContextImpl.startService(ContextImpl.java:1940)
at android.content.ContextWrapper.startService(ContextWrapper.java:843)
at com.liulishuo.filedownloader.services.BaseFileServiceUIGuard.bindStartByContext(BaseFileServiceUIGuard.java:167)
at com.liulishuo.filedownloader.services.BaseFileServiceUIGuard.bindStartByContext(BaseFileServiceUIGuard.java:129)
at com.liulishuo.filedownloader.FileDownloadServiceProxy.bindStartByContext(FileDownloadServiceProxy.java:115)
at com.liulishuo.filedownloader.LostServiceConnectedHandler.dispatchTaskStart(LostServiceConnectedHandler.java:138)
但是不是稳定出现，只有少数情况下会出现。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with FileDownloadServiceProxy.bindStartByContext(), BaseFileServiceUIGuard.bindStartByContext(), and LostServiceConnectedHandler.dispatchTaskStart(), using the Android 15 stack trace as the entry point. Investigate why starting SeparateProcessService sometimes reports a bad process and reproduce the intermittent failure if possible. Done means the cause is identified and the Android 15 service-start failure is fixed or clearly documented.
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
- 30/100