![]() ![]() The customer must discover the problem and bear the data loss. And more. Serif don't even think they should acknowledge this risk and their own huge mistake in that the UI, when it can, warns customers not to store on such devices, drives or services. Serif Software made the catastrophic error to build the Affinity suite upon a totally flawed file architecture and archaic naive OS integration. The year is 2023 and cloud services are the to go solution for many and a standard. Saving to Dropbox and iCloud is also an issue and that is where the issue just explodes. Until then, I know with jpegs you can sometimes retrieve data, repair the file by replacing the header of the file from a good file to the corrupt file using a hex editor not an app for the faint of heart lol! (always work on a copy kids ) but maybe this path is a possible option for repair in Affinity files too. In general the problem appears to occur when saving to and from a network or external drive, Affinity need to make saving a file more robust. Having said that "not supported" posts only account for 0.29% or thereabouts, of the posts made on the forum. I am doing serious work in Affinity v2, but to each their own. I'm unaware of any rash of reports of a similar "not supported" bug in 2.0.3. ![]() I was referring specifically to the "file type is not supported" error when opening Affinity files which is what this thread is about. ![]() Forgot to ask, are you using 2.0.3? If not, please update Affinity as there was a known bug fixed in 2.0.3 that caused this error message. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |