Bryan Rieger

@BlackSkin Messiah hopefully @Callum can help sort this out for you. I don't have v1 installed, otherwise I'd offer to copy/paste from v2 to v1 and back-save to the older format. At least if they can be opened it should be possible to recover the files in some manner. Good luck!

Your file opens fine for me in V1 (and in V2), so all is not lost
I have resaved and uploaded the file you attached (in V1)
See if that opens for you
 
MUTINHIMIRA LOGO-resaved.afdesign

@BlackSkin Messiah hopefully @Callum can help sort this out for you. I don't have v1 installed, otherwise I'd offer to copy/paste from v2 to v1 and back-save to the older format. At least if they can be opened it should be possible to recover the files in some manner. Good luck!

I'm not getting any crashing when deleting brushes, but for me the apps regularly crash while manually importing brushes from 3rd parties such as Frankentoon, Retro Supply Co, and True Grit Texture Supply. While the apps crash, the brushes have actually been imported and are actually present when the app is restarted. This isn't a new bug, it's been with 2.x from the very start.
It's a rather confusing user experience, and I suspect one that new users will find very frustrating.
FWIW I don't purchase anything from the Affinity store beyond the Affinity apps themselves, as I prefer to buy all brushes, assets, etc directly from the 3rd parties that produce them. So for me, everything is installed manually, and crashing on import is sadly a much too common part of my Affinity workflow now on iPadOS.

Sadly! - I can only guess/assume here that the team wanted to throw out a release, as it was somehow under time pressure since some people here in the forum are always pushing for new releases and features. The consequences and effects of this pushing are currently apparent. - I can only advise users to be a little bit more patient in general while waiting for new releases and so giving the dev team overall more time, because the more essential bugs are fixed beforehand, the more stable and usable the applications will generally be.

This bug happens to both Designer and Photo. When you attempt to delete any brush pack, no matter the size, both apps just freeze. When you close and restart them, the brushes are still there.
By the way, importing brush packs still crashes both Designer and Photo. However, after launching teh apps again, the brushes that caused the crash are installed.
- Enrique
 

Yeah, I recall lots of those 'discussions' back then. I never really cared what tools folks used, just as long as they got the job done. That said, if somebody's choice of tool negatively impacted others in the pipeline, that was another matter (as was the case then). I'm happy to see the diversity today, but less so seeing work locked into cloud services with no meaningful way of migrating should the need arise.
Linea is great for brainstorming. Procreate is my driver for illustration work, and I rely on the Affinity suite to bring it all together.

Possibly, but not necessarily. Pages doesn't have "3D support" per se, but rather the ability to embed, render and manipulate (in a very basic manner) these assets. It can't actually manipulate the objects themselves, alter geometry, change materials, lighting, etc (that would need to be done in Blender, Maya, Cinema4D, etc), but it can set basic parameters of the 'scene'; position, rotation, and scale—most of which (with the exception of 3D rotation) are common to any Pages display element.

I'm not being defensive Albert, but you you did ask "Does anyone have thoughts on why it [Affinity Designer] isn't considered more often for this type of [UI/UX] design?
As someone with 25+ years working in UX/UI design with freelancers, agencies, and large orgs, these are my thoughts.

Use the Slices Panel's Clubhouse Sandwich/Hamburger menu in the Export Persona.

@NathanC yeah, this reliably happens if I have previously opened the apps in the larger monitor first. The next time I open them on my laptop without the additional screen the app windows are huge and off-screen. It appears as though the app is restoring the windows to its previous dimensions and position regardless of the display it's on. Going from a smaller to larger screen works fine as the app starts with a smaller window, but going from a larger screen to a smaller results in this problem.
Steps to reproduce:
Connect MacBook to a larger secondary display. Open an Affinity app, make the app fill most or all of the screen. Unplug the secondary display. You can either close the app first and then re-open it, or leave it running. Results are largely the same. Re-open the app if you've closed it. The app window should now extend beyond the screen size, positioned relative to where it had been on the larger display. FYI I'm working on a 14-inch, 2021 MacBook Pro with 32GB RAM running on an M1 Pro chip. The secondary monitor is an LG 27" connected via a standard USB-C cable.
Plea for help.
This bug I can workaround, the following bug I can't as it has me pretty much at a standstill as the UI keeps shifting around making it impossible to work. It's also not limited to Publisher, but all three Affinity 2.2 apps.
 

No, as they are completely different.
I would suggest you look in the Mac App Store and make sure you don't see that you have purchased Affinity Photo 2 from there. Even though you say you purchased from Serif, with V2 you can download from either Serif or the MAS, and if you managed to download from the MAS it would not have the Check for Updates in the application menu.

One of the big challenges Serif has with their UI/UX is that they chose to roll their own UI framework (on macOS it's libcocoaui.framework) and components, rather than use the standard platform frameworks and components (or an established cross-platform UI framework such as Qt). As a result, not only do they not get to benefit from enhancements and additions made to the underlying platforms by the OEMs, but they are now also tasked with the Sisyphean task of maintaining and updating their own framework and components in a never-ending attempt to keep up with basic hygiene, UI/UX guidelines, best practices, etc across all of the platforms they support.
While there's nothing wrong with creating and maintaining a whole new UI framework and component set, it does beg the question of whether the required resources for this endeavour wouldn't be better utilized focusing on your actual products. I do get the attraction of using an abstraction layer across platforms, but the danger in this is that you end up with a user experience that doesn't feel quite right anywhere (just try customizing the app toolbar on macOS, dragging items around is PAINFUL compared to almost every other macOS app[1]). 
Edit
[1] It appears the app toolbar received some attention in 2.2 as it's not nearly as painful to use as it was. Still a few quirks, but the customize feature generally works much more like a standard macOS app toolbar now. 🙏
I wish Serif would take the opportunity with their milestone releases such as 2.2 to not only list the new features they've added, but to also share what bugs they've addressed (especially the long standing ones) as not everyone reads the beta notes. It may seem like a minor thing, and you may feel there are far too many to list, but quite honestly fixing the app minimize behaviour along with the customize app toolbar feature feature on macOS (both fixes shipped in v2.2) are far more important to me than any of the new 2.2 features. It would also clearly communicate how Serif is working hard to both fix bugs (including long standing ones) and release new features.

It should be simple to downgrade the macOS apps, by downloading the older installer files from https://affinity.store/update/macos/appname/2 where appname is publisher, photo, or designer. You can then uninstall the 2.2 apps you currently have installed, and install the older ones. This should not affect your brushes, etc. as far as I know, but there's no guarantee, so you might want to make sure you have a good system backup first. 
There's no way that I know of to downgrade the iPad apps, though.

One of the big challenges Serif has with their UI/UX is that they chose to roll their own UI framework (on macOS it's libcocoaui.framework) and components, rather than use the standard platform frameworks and components (or an established cross-platform UI framework such as Qt). As a result, not only do they not get to benefit from enhancements and additions made to the underlying platforms by the OEMs, but they are now also tasked with the Sisyphean task of maintaining and updating their own framework and components in a never-ending attempt to keep up with basic hygiene, UI/UX guidelines, best practices, etc across all of the platforms they support.
While there's nothing wrong with creating and maintaining a whole new UI framework and component set, it does beg the question of whether the required resources for this endeavour wouldn't be better utilized focusing on your actual products. I do get the attraction of using an abstraction layer across platforms, but the danger in this is that you end up with a user experience that doesn't feel quite right anywhere (just try customizing the app toolbar on macOS, dragging items around is PAINFUL compared to almost every other macOS app[1]). 
Edit
[1] It appears the app toolbar received some attention in 2.2 as it's not nearly as painful to use as it was. Still a few quirks, but the customize feature generally works much more like a standard macOS app toolbar now. 🙏
I wish Serif would take the opportunity with their milestone releases such as 2.2 to not only list the new features they've added, but to also share what bugs they've addressed (especially the long standing ones) as not everyone reads the beta notes. It may seem like a minor thing, and you may feel there are far too many to list, but quite honestly fixing the app minimize behaviour along with the customize app toolbar feature feature on macOS (both fixes shipped in v2.2) are far more important to me than any of the new 2.2 features. It would also clearly communicate how Serif is working hard to both fix bugs (including long standing ones) and release new features.

One of the big challenges Serif has with their UI/UX is that they chose to roll their own UI framework (on macOS it's libcocoaui.framework) and components, rather than use the standard platform frameworks and components (or an established cross-platform UI framework such as Qt). As a result, not only do they not get to benefit from enhancements and additions made to the underlying platforms by the OEMs, but they are now also tasked with the Sisyphean task of maintaining and updating their own framework and components in a never-ending attempt to keep up with basic hygiene, UI/UX guidelines, best practices, etc across all of the platforms they support.
While there's nothing wrong with creating and maintaining a whole new UI framework and component set, it does beg the question of whether the required resources for this endeavour wouldn't be better utilized focusing on your actual products. I do get the attraction of using an abstraction layer across platforms, but the danger in this is that you end up with a user experience that doesn't feel quite right anywhere (just try customizing the app toolbar on macOS, dragging items around is PAINFUL compared to almost every other macOS app[1]). 
Edit
[1] It appears the app toolbar received some attention in 2.2 as it's not nearly as painful to use as it was. Still a few quirks, but the customize feature generally works much more like a standard macOS app toolbar now. 🙏
I wish Serif would take the opportunity with their milestone releases such as 2.2 to not only list the new features they've added, but to also share what bugs they've addressed (especially the long standing ones) as not everyone reads the beta notes. It may seem like a minor thing, and you may feel there are far too many to list, but quite honestly fixing the app minimize behaviour along with the customize app toolbar feature feature on macOS (both fixes shipped in v2.2) are far more important to me than any of the new 2.2 features. It would also clearly communicate how Serif is working hard to both fix bugs (including long standing ones) and release new features.

Wow @MikeTO this is phenomenal. Thanks for sharing this. Not only is it a pleasure to read, not only can I add notes and annotations, but I'm also learning a ton. Kudos!

Updated for Publisher 2.5 (May 2024)
Publisher Manual May 23 2024.pdf
This free in-depth manual is filled with steps, tips, and recommendations for:
Documents, Pages, Master Pages, Sections, and Baseline Grid Character and Paragraph Formatting Text Styles (paragraph and character) Text Frames, Text Flow, and Stories Images and Picture Frames Books and Chapters Cross-References, Table of Contents, and Index Notes - including Footnotes, Sidenotes, and Endnotes Fields - including Page Numbering, Running Headers, and Custom Variables Anchors and Hyperlinks Printing and Exporting Settings New for this edition: Getting Started, Variable Fonts, and more This manual does not cover illustration and photo editing.
Q&A
Is this really free? Yes, it's copyrighted only to prevent others from publishing it as their own Is there a longer manual I can purchase? No Is there a version for Designer or Photo? No, but many of the features are the same so it will still be relevant Is there an iPad version? No, the steps and screenshots are for the macOS and Windows versions Why does it use a print layout if it's a PDF? It's a demonstration of how to use the features it describes to create a print book You might also like:
Special Characters Quick Reference Chart: https://forum.affinity.serif.com/index.php?/topic/176386-special-characters-in-affinity-quick-reference-chart/ Terminology Translation Dictionary for Dutch, Polish, Ukrainian, Swedish, Norwegian, Danish, and Finnish: https://forum.affinity.serif.com/index.php?/topic/209953-terminology-translation-dictionary/ Previous 2.4 manual for those who still want it:
Publisher Manual Feb 26 2024.pdf
 

I dont use them either. This is a tablet. The ipad app is designed for everything close to you for easy toggling. Hand gestures are introduced. I dont need to press command + d to deselect. i don't need a shortcut to change my blend modes. i dont need to press command +4 to zoom in at %800. i have a hand gesture for Zoom.
this is a tablet. im building things with my hand and pencil. not a mouse and keyboard. i guess theyre there for other users if they want to work that way. not me though. 
I'm sorry about how youre feeling, my friend. I understand you so much. I love this app so, SO much. I believe it too. 

This issue with the Toolbar or Context Bar being cut off on macOS is a known issue. It can happen for a number of reasons but one is just loading a Studio preset with a different combination of those items being shown/hidden.
Reset Studio will fix it. This command on macOS resets the Toolbar, Context Bar, Tools panel, and left and right Studios.

Thanks @walt.farrell and @Return, the view options are ticked as expected. I guess ctrl run up it is. Sigh.

I get you walter but its deeper than that. Its way deeper than that. Its design. Its not just education. Its design. I shouldn't have to educate myself to do basic actions. These are controls/attributes that we're talking about. Not tools and studios. I dont need serif to spell out every tool and studio because those can be translated into simple icons. Thats why we have to tool and studio bar. These are controls and attributes that we're talking about. These CAN NOT be translated into icons. You can not translate offset, radius, and intensity into icons and expect users to know what they are. You can not tell us to tap the ? icon and make us work this way all the time because serif couldnt spell out attributes/controls. 
Sigh. If serif wants us to "educate ourselves" its still bad design. It is still bad design to have sliders on the left and the context bar at the top. Its all bad design. Your explanation doesnt justify all the reasons and logic I left on this post for serif to keep this new context control design in v2. Again, its deeper than serif wanting us to educate ourselves. Its design. Its all bad design. Serif cant be hiding attributes within sliders. Serif cant be playing hide and go seek with their users. You cant. Its bad design. The bad design still remains in the app. Its going to stay there and confuse users. The ? button doesnt justify the bad design. 
 
 

Hi, I believe this issue has been around since 1.x and somebody else reported it again during the beta. It's not specific to Publisher, but once your studio get into this state in one of the apps you can keep experiencing this sort of issue in that app.
I recommend fixing your Publisher studios by choosing Window > Studio > Reset Studio, setting up your studios again the way you like them, and then saving that as a preset by choosing Window > Studio > Add Preset...
Cheers

I see this was not addressed in v2.2
This is... aggravating.