[X] I've checked that there is no other issue about this feature request.
[X] This issue contains only one feature request.
[X] The title of this issue accurately describes the feature request.
Feature description
This is technically two feature requests in one, but I believe that it is worthy to mention both options since I believe that one would be the better. First route, instead of blindly taking the backup and causing it to crash indefinitely, it will tell the user that backups made on forked versions of the InnerTune application aren't compatible. Second route, implement tools like the InnerTune Backup Fix into the application and if it detects a backup that was curated on a forked version, it will automatically convert it to a backup that it'll be able to digest.
Why do you want this feature?
When the original developer of the application stepped away and stopped maintaining the project, many individuals stepped up and curated forked version of the application, an unofficial passing of the touch. This includes Malopeids' version and many others. Though now that the original developer of this application has returned and resumed with maintaining the project, many users may want to switch back to this version of the application (for whatever reason they may have.)
Right now, when they go to restore a backup using a backup curated in that forked version, there's a non-zero chance that the application will not only not accept it, but go into a state of indefinitely crashing. Of course, some people may know that the solution to the problem is to just clear the storage associated with the application. But for those who don't, they may just turn around and think that the original project is entirely broken (through no fault of the developer.) So having a tool that automatically converts it to something that is compatible (in-app) would be nice for users who are wanting to make that switch (and may not be aware of the InnerTune Backup Fix website/project that is separate to this project/application.)
Checklist
Feature description
This is technically two feature requests in one, but I believe that it is worthy to mention both options since I believe that one would be the better. First route, instead of blindly taking the backup and causing it to crash indefinitely, it will tell the user that backups made on forked versions of the InnerTune application aren't compatible. Second route, implement tools like the InnerTune Backup Fix into the application and if it detects a backup that was curated on a forked version, it will automatically convert it to a backup that it'll be able to digest.
Why do you want this feature?
When the original developer of the application stepped away and stopped maintaining the project, many individuals stepped up and curated forked version of the application, an unofficial passing of the touch. This includes Malopeids' version and many others. Though now that the original developer of this application has returned and resumed with maintaining the project, many users may want to switch back to this version of the application (for whatever reason they may have.)
Right now, when they go to restore a backup using a backup curated in that forked version, there's a non-zero chance that the application will not only not accept it, but go into a state of indefinitely crashing. Of course, some people may know that the solution to the problem is to just clear the storage associated with the application. But for those who don't, they may just turn around and think that the original project is entirely broken (through no fault of the developer.) So having a tool that automatically converts it to something that is compatible (in-app) would be nice for users who are wanting to make that switch (and may not be aware of the InnerTune Backup Fix website/project that is separate to this project/application.)
Additional information
No response