Lirico wrote:It may be that you do not have any application of the type "apks", that's why you have no problem. As I said before, when I wanted to restore an application of the apks type the process never ended, when I saw that problem I said "goodbye titanium backup"

For a few years I use Swift Backup (it is paid and can not be hacked) and I have no problem.
As written before: if you have trouble, than just use it for data backup/restore. Install the Apps the regular way, than everything should be fine.
I dislike dependency on Google Drive. Tested Swift Backup, 3C and some other Root Backup Apps a while ago, but wasn't very satisfied with it. However I will keep it in mind for the time TB will stop working at all.
Also for APKs: This is the new way of installing to reduce needed storage and maybe loading time. Old APK files had every Architecture (ARM v6, v7a, v8,...) and DPI included and installed everything on your phone as such. Now in new APKs the App is separated from most libraries. APKs are old APK slimmed down with every library file separately in it. This makes the "APKS" file itself bigger, but if you install it, it will only install the libraries necessary for your device nothing else. You won't have any ".apks" file installed only typical ".apk". You could say apks are only Installer files.
If you got problems with such files the cause must be different. If you transferred to another device, maybe the correct library files where missing, because the old device used others?
How can Swift Backup avoid it?
I don't know, but if using online, my
guess would be that it installs Apps the regular way and only restores your data afterwards, so same as I suggest for TB but automatically not manual.