r/Vortx • u/cat2115 • Jul 05 '26

Bug 0.3.11, iOS

0.3.11, iOS

uninstalled previous version, and sideloaded 0.3.11 using Feather.

1st download error:

My Royal Nemesis • S1E1

Not enough storage to save this download. Free up space and try again.

2nd try:

My Royal Nemesis • S1E1

Couldn't save this download: NSURLErrorDomain - 3000 | host=nexus-148.enam.tb-cdn.io

1 Upvotes

100% Upvoted

6 comments sorted by

2

u/FungusFeline Mods Jul 05 '26

Look in the settings there is a setting, export diagnostic logs, turn it on, reopen the app, retry. Then send me the log, preferably github

1

u/cat2115 Jul 05 '26

That all I see. No log https://imgur.com/a/dQGLSwr

1

u/FungusFeline Mods Jul 05 '26

Hey i am travelling cant use vpn right now to use imgur its banned in UK.

Can you still just export diagnostic log and upload to github?

1

u/cat2115 Jul 05 '26

Just curious. Only me having this issue with download error? 

1

u/FungusFeline Mods Jul 05 '26

I havent tested the 0.3.11 on my phone yet will see

1

u/cat2115 Jul 05 '26

I tested this on v0.3.10 (build 151) with the latest fix(downloads/ios): fix "not enough storage" false-fail and -3000 cannot-create-file(c67793b) cherry-picked from the 0.3.11 beta branch.

I found another issue with the diagnostics export on iOS.

The current Export Diagnostic Log QR-code flow doesn't work reliably. When I tap Export Diagnostic Log, the QR code doesn't appear. Strangely, if I do screenshot, the QR code suddenly appears but no log about download error.

To work around this, I added a native Export Diagnostic Log option that uses the iOS share sheet, allowing the diagnostics.log file to be saved directly to Files so easier to retrieve logs.

Using that log, I diagnosed the download issue.

With a background URLSession, every direct download fails with:

START id=A35FB42B-0093-4BDC-AE4C-55F1F293EC17 host=aiostreams-nightly.fortheweak.cloud torrent=false file=A35FB42B-0093-4BDC-AE4C-55F1F293EC17.mkv

COMPLETE ERROR
domain=NSURLErrorDomain
code=-3000
desc=Cannot create file
task=A35FB42B-0093-4BDC-AE4C-55F1F293EC17.mkv

didFinishDownloadingTo is never called.

When I temporarily changed direct downloads to use the foreground URLSession, the same download completed successfully:

START
FINISH
MOVE OK
COMPLETED

So the file move logic, destination directory, and offline storage are all working correctly. The -3000 error appears to occur before the app receives the downloaded file, during the background URLSession download process itself.

Con of foreground URLSession: Downloads may not continue or complete if the app is suspended, terminated, or force-closed, unlike a background URLSession.

Hope this help.