Dan Cross

I’m waiting for further updates because at this point transfer between desktop and ipad feels dangerous

I’ve tried the beta and it won’t open even the file that your team fixed internally ( which now works on my Mac mini m1 desktop and I saved the file on my external drive to avoid cloud sync corruption. I’ve sent several crash reports using the betas

I will check that out, thank you

It worked on my desktop but not on ipad

By the way I’m using iPad 16.2 iPad (9th generation) MK2K3LL/A K73X3D4N93 my desktop is a mac mini m1

I actually switched my desktop to a Macintosh. I was so frustrated with the windows version and switched my licenses to the Macintosh desktop. Unfortunately, the files still did not open on that but this new file you sent me I will try a little bit later when I get to my office.

Unfortunately it did not open. I exported it directly to my local storage for fear it would get corrupted again if this has anything to do with cloud storage; but to no avail. This time the file crashed the program. After I clicked “open” through Publisher for Ipad’s menu selected the file, the entire app vanished after a brief showing of the word “opening”

I cannot open a single one of any iterations of my layout file now, whether .apackage or .apub, regardless of whether it is in Dropbox, Icloud, or local storage. All the same version error. I have been working on this project for a year and now I have no access to it.

I have tested this issue with several different cloud drives too. Once problems began with a file, however, it made no difference if I transferred it to my iPad manually or not. I hope my .apub files are not damaged.

This is exactly what I am facing, and it gives me the same error on Windows, Mac and iPad OS. I am crippled by this. I tried to revert back to V1 and of course that didn't work either (which I guess should be expected).

I hope they fix it soon! I feel sad about this!

Ipad cannot open files—says doc is from a newer version but the file was saved from in Publisher 2 Desktop for windows. Does not matter if it is opened from cloud or file transferred directly through ITunes…same result. I hope this gets fixed quickly.

Is this one of the issues you are aware of? Because this is crippling.

It does open fine on desktop.

My Publisher file is claiming that I am missing a font on my Ipad (and Desktop) version that I have installed on both places. All other fonts are recognized and work fine. When I try to search for the missing font by name in the document itself it brings up nothing (using search by format). Also, when I try to click "fix" in the preflight window it brings up the fonts dialog box but that font is not listed at all. How do I resolve this?

I can try using Itunes for Windows and move the file from desktop that way (making sure all images are embedded because otherwise I still have issues with linked resources and unable to “authorise” their image folders. [later now] I noticed that when I transfered a file using Itunes it showed the Icon for Photo V2 in Itunes. Not sure if that points to a problem or not. So I updated the file and transferred using iTunes from my desktop. Unfortunately, I got the same error message.

No, it is happening with icloud files or even local storage if I move the file to that location (I was just experimenting). Part of the message is that it "includes features from a later version of Affinity". I save the file on my desktop first, then try to open it it in the Affinity Publisher for Ipad, and both are V2, so I wonder how it could be flagged as a file containing features from a later version?

I can’t open anything

I’m having trouble opening files all around it seems. Here is the latest. Ugh!

What happens is that I'll tap authorise and it will always open to the Files app. I'll navigate to the folder where the images are, choose that folder, and then the only open is to tap on "open". I do so and it returns to Publisher, at which point the same dialog appears for the same file. If I hit ignore it does it with the next "linked resource sandbox error" image. The short-term solution for me was to embed every image and save a copy of that to my icloud before trying again. But that was a workaround, so I'd like to know what else I could do.

I have it sync'd right now with icloud. Could the very existence of the Google Drive be affecting things somehow?

Hey Mac Mini m1 users: Do you feel the Mac Mini M1 is sufficient for multitasking using multi-monitors while using Affinity V2 programs together?

Unfortunatley, after I successful made the shortcut, I opened my file and still got the "linked resource permission denied" message with the "linked resource sandbox error" in preflight. Darn!

Thank you so very much!

No external hard drive. I have had the same problem using google drive versus icloud, and also experiencing the same issue with Dropbox. I am thinking your shortcut suggestion will work if I can get it structured correctly in Shortcuts syntax wise. That is because he file in question was originally a V1 on desktop…however, I did open and resave in in v2 of Publisher desktop first, before opening. And I did use the open dialog box from within the app itself.