Closed mrdebugger007 closed 11 months ago
-help needed
@mrdebugger007 Thanks for pointing out this bug. Could you test again with version 16.8.1 from the link below to confirm that this bug is resolved?
@mrdebugger007 Thanks for pointing out this bug. Could you test again with version 16.8.1 from the link below to confirm that this bug is resolved?
The issue with the percentage has been resolved, however, it has caused two new issues to arise. Firstly, the loading process stops automatically after reaching around 65% or 67% is it the expected behavior? Secondly, the app is not responding properly when attempting to access a folder or click on any items, displaying a message but no action occurs.
This video shows what's happening:
Edit: edited youtube video link
[...] the loading process stops automatically after reaching around 65% or 67% is it the expected behavior?
Yes. The previous problem was caused by the missing Content-Length header in the response, so the program couldn't calculate and display any progress.
So, for these cases, I hardcoded a dummy size corresponding to a large list (100MB) to display progress (even if inconsistent) to the user, which seemed less tedious and frustrating for the user.
As a side effect, the download of the list may finish before 100%, if the list is smaller than the estimated size, or stay at 99% for a long time at the end if the list is much larger.
[...] Secondly, the app is not responding properly when attempting to access a folder or click on any items, displaying a message but no action occurs.
That was a silly logic error that somehow got unnoticed in the commit. Sorry about that.
This bug was fixed in commit v16.8.1-rev2 and installers were updated in the pre-release below.
[...] the loading process stops automatically after reaching around 65% or 67% is it the expected behavior?
Yes. The previous problem was caused by the missing Content-Length header in the response, so the program couldn't calculate and display any progress.
So, for these cases, I hardcoded a dummy size corresponding to a large list (100MB) to display progress (even if inconsistent) to the user, which seemed less tedious and frustrating for the user.
As a side effect, the download of the list may finish before 100%, if the list is smaller than the estimated size, or stay at 99% for a long time at the end if the list is much larger.
[...] Secondly, the app is not responding properly when attempting to access a folder or click on any items, displaying a message but no action occurs.
That was a silly logic error that somehow got unnoticed in the commit. Sorry about that.
This bug was fixed in commit v16.8.1-rev2 and installers were updated in the pre-release below.
When attempting to load an m3u file using a URL, the loading percentage reaches 67% and then resets back to 0%, causing the list to reload multiple times.
Video: https://youtu.be/enEvpDKLPOI
Additionally, even after successfully loading the list multiple times, some channels do not play correctly and either display an error message about a broadcaster issue or a black screen. However, when attempting to play the same channels on a different app, they work without issue.
The video is set to play at 2.5x speed. Video: https://youtu.be/mivKbLFELQ4
Ps: After loading lists app size is going over 1GB.
@mrdebugger007 Could you test again with version 16.8.4 please?
@mrdebugger007 Could you test again with version 16.8.4 please?
Still same issue.
@mrdebugger007 The issue is resolved in the current version. If you notice any other problems please let me know.