[GH-ISSUE #65] Compactability between version 3.X and 4.3 #61

New issue

Open

opened 2026-02-27 19:03:18 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 19:03:18 +03:00

Owner

Originally created by @ryusakura on GitHub (Jan 15, 2026).
Original GitHub issue: https://github.com/afkarxyz/Twitter-X-Media-Batch-Downloader/issues/65

I found myself unable to migrate from version 3.X to 4.3 as per the following problems, making me still staying on version 3.X

First of all I need to import the list manually
When I exported all data from 3.X to 4.3, all files need to download again as it unable to recognize the file I had downloaded. Which it first making the folder name for each user from "image" to "images" and etc.
When I starting to fetch, I found many of the user failed with unknown reason, which it still available on version 3.X

Originally created by @ryusakura on GitHub (Jan 15, 2026). Original GitHub issue: https://github.com/afkarxyz/Twitter-X-Media-Batch-Downloader/issues/65 I found myself unable to migrate from version 3.X to 4.3 as per the following problems, making me still staying on version 3.X 1. First of all I need to import the list manually 2. When I exported all data from 3.X to 4.3, all files need to download again as it unable to recognize the file I had downloaded. Which it first making the folder name for each user from "image" to "images" and etc. 3. When I starting to fetch, I found many of the user failed with unknown reason, which it still available on version 3.X

kerem commented

2026-02-27 19:03:18 +03:00

Author

Owner

@asdfghjkkly commented on GitHub (Jan 15, 2026):

Similar to #3 in comments by @ryusakura:

I'm finding that Fetch typically fails when attempting to update any account that has been downloaded before.
It occurs especially if there are over 1000 posts. Increasing Fetch Timeout does not resolve it.

Deleting the account from Batch-Downloader and running it anew is a reliable workaround.
Not sure why it makes a difference.

The Fetch issue is not an authentication error and not a limit max. It seems to be connected to an inability to read certain timelines (though not others).

Thanks for this wonderful program, by the way! Even with the issue, it's still the best around, and clearly it is a lot of good work that gets it to the level! Very VERY appreciated!!

@asdfghjkkly commented on GitHub (Jan 15, 2026): Similar to #3 in comments by @ryusakura: I'm finding that Fetch typically fails when attempting to update any account that has been downloaded before. It occurs especially if there are over 1000 posts. Increasing Fetch Timeout does not resolve it. Deleting the account from Batch-Downloader and running it anew is a reliable workaround. Not sure why it makes a difference. The Fetch issue is not an authentication error and not a limit max. It seems to be connected to an inability to read certain timelines (though not others). Thanks for this wonderful program, by the way! Even with the issue, it's still the best around, and clearly it is a lot of good work that gets it to the level! Very VERY appreciated!!