-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backup from 3.6.5 not working in 3.7.0 #196
Comments
Without giving any personal info, can you show the structure of the file you are trying to import in version v3.7.0? As for the new account method, using regular Twitter/X account, I'm not a fan also but unfortunately this is now enforced by the Twitter/X API since it is not possible to create guest accounts anymore. |
kinda hard to look into that wacky backup structure and remove my personal data, I'm gonna do that tho when I have the time and let you know |
looks like mine has guest account instead of twitter token so this might be an issue in not loading the backup correctly |
… created for tokens and profiles. Also do a better management of the tokens that have been marked as rated limited for a while.
The version v3.7.2 fixes this issue. |
yes 👍 :)) |
Checklist
Affected version
3.7.0
Steps to reproduce the bug
Expected behavior
import all the subscriptions and saved posts
Actual behavior
doesn't import anything
Screenshots/Screen recordings
No response
Logs
No response
Affected Android/Custom ROM version
No response
Affected device model
No response
Additional information
the backup works with previous versions of squawker, I think it's 3.6.4 / 3.6.3 anyway I think it is the last version from 17.01.2024 (date of the backup that works) the backup made within 3.6.5 can be imported successfully in 3.6.5 but not in 3.7.0 and it doesn't even give me the check that data was imported successfully. I'm not a fan of the new account method since I think it makes it less privacy oriented app because you need a X account now while on the other versions you don't need any account to browse twitter.
The text was updated successfully, but these errors were encountered: