danikula / danikula/AndroidVideoCache

Other languages can't play

Open
#174 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
5.5k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

Error Messge:

Error reading ping response
com.danikula.videocache.ProxyCacheException: Error opening connection for http://127.0.0.1:58711/ping with offset 0
at com.danikula.videocache.HttpUrlSource.open(HttpUrlSource.java:75)
at com.danikula.videocache.Pinger.pingServer(Pinger.java:86)
at com.danikula.videocache.Pinger.access$100(Pinger.java:28)
at com.danikula.videocache.Pinger$PingCallable.call(Pinger.java:108)
at com.danikula.videocache.Pinger$PingCallable.call(Pinger.java:104)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.io.FileNotFoundException: http://127.0.0.1:58711/ping
at com.android.okhttp.internal.http.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:197)
at com.danikula.videocache.HttpUrlSource.open(HttpUrlSource.java:70)
at com.danikula.videocache.Pinger.pingServer(Pinger.java:86) 
at com.danikula.videocache.Pinger.access$100(Pinger.java:28) 
at com.danikula.videocache.Pinger$PingCallable.call(Pinger.java:108) 
at com.danikula.videocache.Pinger$PingCallable.call(Pinger.java:104) 
at java.util.concurrent.FutureTask.run(FutureTask.java:237) 
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) 
at java.lang.Thread.run(Thread.java:818) 

Pinger: Error pinging server (attempts: 3, max timeout: 280). If you see this message, please, email me danikula@gmail.com or create issue here https://github.com/danikula/AndroidVideoCache/issues
com.danikula.videocache.ProxyCacheException: Error pinging server (attempts: 3, max timeout: 280). If you see this message, please, email me danikula@gmail.com or create issue here https://github.com/danikula/AndroidVideoCache/issues
at com.danikula.videocache.Pinger.ping(Pinger.java:67)
at com.danikula.videocache.HttpProxyCacheServer.isAlive(HttpProxyCacheServer.java:187)
at com.danikula.videocache.HttpProxyCacheServer.getProxyUrl(HttpProxyCacheServer.java:119)
at com.danikula.videocache.HttpProxyCacheServer.getProxyUrl(HttpProxyCacheServer.java:100)
at com.lvfq.ekoomvp.util.musicplay.PlayService.startMp3(PlayService.java:149)
at com.lvfq.ekoomvp.util.musicplay.PlayService.access$100(PlayService.java:44)
at com.lvfq.ekoomvp.util.musicplay.PlayService$2.run(PlayService.java:113)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:5942)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1400)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1195)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the playback failure, then read Pinger.java and HttpUrlSource.java around the reported connection error. Trace the call through HttpProxyCacheServer.java and PlayService.java, and compare behavior for the affected languages. Done means the failing playback path is identified, corrected, and verified without the ping error.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile-dev
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.