dagen

Ok… I checked the exact Version number (20C65) which is a RC… despite this I don’t think this is the cause of the issue. This is interesting… Your iPad (2018) does have the A15 or 16 chipset… So mine has the M1…,. There are some changes in the overall hardware, as well as display since the 2018 model… mine’s a 2021 (A2459) 5G model (Apple calls it WiFi+Cellular) However assuming you have the 11” too, the display resolution between yours and mine is unchanged… Is anyone here having the same issues with a iPad Pro 11 Gen3 (M1… or maybe the newer M2)? I’ve tried a bunch of things: - Changing the Display zoom settings - disabling Stager Manage - forced restart - deleting the app and re-installing - with stage manage ON, manually resizing and dragging the window (this forces most apps to re-draw the UI) - Switch between dark-mode / light-mode - different files… Nothing changes the fact, that the export dialog is pretty much broken on my system

as of this morning…. used to say “16.2beta4” yesterday… noticed the update itself was also no longer with the BETA tag… so this is 16.2 apparently.ö To be fair, I can’t recall if apple on the public beta does actually label the final RC version as such (But I assume they do) i need to check up the actual version number to see whether this is the final version or a RC (release candidate) Usually though RC with apple is a pretty stable thing and there’s often only absolutely small-ish bug-fix things between the RC and the full version release. Unlike Beta which tends to be buggy especially in the fist one or two iterations. I’ve used Apple beta software for a long while, and usually RC is pretty close to the official release. Not saying - if it’s actually an RC - that it can’t contain bugs. Again, I’ll need to look up the actual version number and look at the release notes, then I’ll see whether it’s RC or full.

First: thanks for the support mail info… I’ll send one in a bit. the Beta: I had just mentioned it in the last post: I’m no longer on the beta - just installed the final 16.2 version that has just been released here….. and the problem still exists. Also it’s with every of the v2 affinity apps - no other ipad app I have has a similar issue… so this is definitely an affinity issue.

Is there anyone from Affinity reading this? Frankly my EXPORT Dialog is pretty much useless…. I’ve now updated my iPad Pro 11 M1 to the latest iPadOS 16.2 - and the issue still persists. I had sort of hoped/assumed it was part of the beta issues - but frankly now that the iPad is on a final version, I think this is a UI Bug with affinity’s line of iPad apps. Same issue in Designer, Photo and Publisher (v2) How is this useful?? I mean frankly, you can get an export done… sort of . with a lot of patience and trial and error. But this is a pretty major bug in my opinion… OR put it like this the apps on the ipad pro (11”, M1, 16.2) are virtually useless this way, as what good does it do if it gives me such a hard time actually getting work OUT of the app. So please, anyone from AFFINITY please fix this, or at least give me some feedback. There’s no support email or anything - it’s this forum or nothing from the looks of it. and there hasn’t been a single “official” reply. Also noteworthy: Affinity v2 apps are the ONLY apps on my iPad that have been doing that… i assume its of course down to affinity framework code… doesn’t look like they use the standard apple ui kit…

No, no need to be sorry this isn’t your doing afterall

That would work if there would be publisher v1 for ipad, alas that never existed (v2 is the first release on the ipados platform. Also this “solution” is so far from any ideal: it means retaining an old version, just to occasionally work on files from older version. But the most difficult part would again be the simple thing: I make a document in v2 - then need to share it with someone who uses v1. end of the line. out of options. Aside from trying to copy/paste the entire document from v2 into publisher v1… or do the PDF thing and loose pretty much all realistic editability… how can this be regarded as a viable “solution” - at best it’s an occasional crude band-aid.

I think that’s pretty much the minimum it needs to do… it would at least have saved me a good bit of work. However I don’t think it solves the underlying issue. From a plain “logic” point of view: 1. create a file in v1 2. Open it in V2 3. edit just basic things (like re-arranging a few text boxes, replacing a few images, etc…) 4. Save it (in v2). there is nothing in that workflow that would mandate a file incompatibility. So when v2. would indeed offer the option to save in a backwards compatible format - nothing should be amiss in that file. Sure if I play with new features etc… when the file is complex, I expect it to loose things - or fail to work to some extend when saved in a “compatibility” format. But NOT having the option at all is pretty weird. again - the software dev side of things, I’m pretty much aware off, having worked a couple of years in software development. I know that sometimes you have to adapt a file format to allow it to handle new things. There’s no way around it. This is something I do fully understand. But I find it highly shortsighted not to offer some sort of compatibility with the previous version. After all it’s “just” one version - not five or 10 in between. Sure at some point, loosing compatibility is “OK” - but not between single version iterations without an option to keep working together with folks who don’t update asap. And sure affinity’s pricing is far more “forgiving” than adobe’s …. you could say the 100 quid (intro offer) for the entire v2 suite is really just a lovely deal (it is in my opinion). But essentially now I’m either being forced to keep working with v1 until the people I collaborate on stuff with upgrade as well… or push the people to upgrade sooner. neither is appealing in my opinion. Sure I think at some points the others will upgrade… but will this repeat with every iteration we see? So here’s my wish for affinity: - Offer a compatibility mode… a feature-reduced file-type that allows back and forth data sharing between V1 & v2 users - or better yet, offer a more open file format for interchanging files… whether this is something like scribus’ XML based files or adobe’s IDML support or whatever… But something, that may take a few issues with complex layouts, but works well for exchanging data between different creators. the last part is something I see as a merit in moden software development - cross platform compatibility. Lots of things we can do work now across multiple platforms, for many things it has become pretty irrelevant whether someone uses windows or mac or iPadOs,… modern Frameworks allow for simplified cross platform development to an extend (it used to be a LOT more work, it still is enough work, especially doing the porting between win/macos thing, but comparatively it’s easier than say 10 years ago). Also with plenty of things available truly platform independent as web-apps cross-compatibility becomes a selling point. often when I look for a software solution to a work-problem I look at offerings based on their cross-platform compatibility, on data export/import etc.. I’ve had a few system changes (win/mac/linux/iOS) and use more than one platform, and not needing to find “new” and individual solutions is really great., that is something that opensource software like gimp, scribus, inkscape, libreoffice, etc… just do a LOT better than most of their commercial peers. And I think it’s a tad sad, that the main reason for this is often a business decision, where a company thinks its great to lock people into their ecosystem (I’m looking at you, apple and your silly lightning plugs… really 2022 and iPhone 14 still has a lightning plug… it takes the EU to force you to lay off it…. and go for the open standard that is USB-C). it often feels the same with proprietary software….

I’ve also went ahead and reset the display zoom setting to normal, and re-tested: same issue: also it doesn’t matter whether the app runs in a scaled window (as above) or in fullscreen - same result. When you click on “export” it all looks fine at first… but every time you click on any format (say you switch from PNG to PDF) it just piles on UI Elements on top of what’s already there… klick on yet another one, and more is piled on… Also this happens in Publisher, Designer - and most likely photos (haven’t tested yet) as well it may be down to the iPadOS BETA I’m running (16.2 beta 4) albeit it’s the only apps (affinity) that seem to have such an issue…

Copy & Paste : well this would work - on my own computer …. but it still means keeping V1 in place… which isn’t possible on the iPad Pro (no v1).. I really think that this is a bit of a serious compatibility issue… I can see why IDML isn’t exactly supported, after all it’s an adobe thing. (not sure how “open” the file format is from a dev point of view). But if it’s anywhere near the same as it used to be with a PSD than it will be a while… Anyhow, I think (as much as I dislike many of their SW-decisions) Microsoft has done this part pretty much spot on with their office-suite: offer to save in an older format. This way it’s MY Choice whether I’m ok with loosing some features in a file - but at least I can make sure that a customer or colleague on the other side of the globe with older versions of a software can still open it. At the very least the software should warn me, that saving the file will prevent older versions from opening it again (afterall, the file I mentioned was created with v1). I would understand this a lot more, if say the current version would be v7 or v9 and backwards compatibility to say v2 would be lost… but one version jump… seems a bit unnecessary.

I’ve set it to “more space”… I don’t see how that could be the issue - as actually that would give the display more space for UI Elements… Also the screenshot shows that essentially all settings for all formats will remain visible, overlaid on top of each other, rather than clearing/refreshing the “tabbed” dialog… Also it does the exactly same thing if I push the app to the external display (stage manager on ext. display).. the ext. display is a 4k Screen, at full resolution without any of the zoom settings (it’s on “normal” ) …

Hi… I‘ve been a long time user of the V1 Apps (on MacOs mostly) and also on iPad Os… and recently upgraded to the V2 apps. the following issue is NOT Exclusive to the iPad - it‘s the same on the Desktop app… Regarding Publisher v2. yesterday I received a Publisher File (made in V1 by someone else) - and proceeded to make a few changes I wanted, then saved it and sent it back. Only to hear back from the recipient in a short time, that she couldn‘t open the File anymore … Apparently the V2 files, same file extension etc… are indeed not backwards compatible at all. that, whilst annoying, would be „understandable“ with feature advancements etc, often in SW-Dev it‘s difficult to achieve a complete backwards compatibility with newer files. I thought, „no Problem“ I just do an export to something else… But there is simply NOTHING I could do that would work. There‘s no option to save the file for an older version (MS Office has been offering that feature for ages)… I‘d be perfectly happy to loose a few features in the file, but give me some option to export it so that someone with an older version (one version) of Publisher can OPEN it …. (especially considering the original file was made with V1) or offer export / Import in both V2 and V1 with a compatibility format, or IDML or whatever …. I‘ve tried to „work around“ the issue by exporting as a PDF… and then sending the PDF and open that in V1. that does sort of work - but you loose pretty much all usable editability (text boxes are one line text-items etc… which makes collaborating on that document pretty much useless.) It also means I had to recreate the changes I had made from scratch in V1 (I used the Macbook which had still both versions installed - if I had only had the iPad at hand it wouldn‘t have been possible at all) … which meant a few hours of work just because version change. Also when someone shares an AFPUB file with me, I have no practical way of knowing whether it‘s v1 or v2… so when I open it in v2 - no problems… but save and share back for some more collaborative work - and if the sender had made it using with V1 they can‘t keep working on it. which means I need to keep relying on V1 - keep a double install … and always make sure to ask whether it‘s from v1 or v2. which also means v2 on the ipad is often out of the question. Sure the „easy way out“ would be to simply „force“ the other parties to buy the V2 apps… and whilst I personally find pricing to be very reasonable, I don‘t think its the solution I‘m looking for.

Same issues here… I‘ve also gone to disable the „Present on External Display“ setting to prevent the issue from happening. however when I have it enabled my external display will show some sort of „print preview“ or something like it, however it‘s pretty useless, it doesn‘t move with the content, I can‘t scroll / zoom or otherwise interact with it - it‘s essentially just some static „preview“ that‘s stuck on whatever it chose to display when the file opened … I guess it‘s due to the Beta ipad os… iPad OS 16.2 beta 4, iPad Pro 11, M1

This is what I often get when I try to export anything from publisher v2 … Depending on the export file format selected, the app will overlay all kinds of export settings ontop of each other… slightly difficult to use this way. iPad Pro 11, M1, running iPad OS 16.2 beta 4 Affinity Publisher v2.0.2