TeamAmaze / TeamAmaze/AmazeFileManager

Crash on bind FtpTileService

Open
#2,648 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-FTP From-Email Issue-Bug
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

Issue explanation (write below this line)

Exception

  • App Name: Amaze File Manager
  • Package: com.amaze.filemanager
  • Version: 3.6.1
  • User Action: UI Error
  • Request: Application crash
  • OS: Linux Android 11 - 30
  • Device: crosshatch
  • Model: Pixel 3 XL
  • Product: crosshatch
Crash log

java.lang.RuntimeException: Unable to bind to service
com.amaze.filemanager.asynchronous.services.ftp.FtpTileService@2d5a252 with
Intent {
cmp=com.amaze.filemanager/.asynchronous.services.ftp.FtpTileService (has
extras) }: java.lang.RuntimeException: Unable to reach IQSService
at android.app.ActivityThread.handleBindService(ActivityThread.java:4228)
at android.app.ActivityThread.access$1600(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1937)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
Caused by: java.lang.RuntimeException: Unable to reach IQSService
at android.service.quicksettings.TileService.onBind(TileService.java:359)
at android.app.ActivityThread.handleBindService(ActivityThread.java:4213)
... 8 more
Caused by: android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(BinderProxy.java:550)
at
android.service.quicksettings.IQSService$Stub$Proxy.getTile(IQSService.java:285)
at android.service.quicksettings.TileService.onBind(TileService.java:357)
... 9 more


Contributor guide

Open the contributing guide

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 by inspecting FtpTileService and the Android TileService binding path referenced in the crash log. Determine whether the failure can be reproduced on Android 11 with the reported quick-settings action, then identify an agreed expected behavior for a dead IQSService connection. The issue provides no failing test, target file beyond the service name, or defined completion condition.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.