Dan C

From the OP description, he's working in a new pixel layer with the Inpainting Tool set to Current Layer & Below thus the Image layer doesn't need to be rasterised - the output will be placed in the new pixel layer. Even if he was working directly with the Image layer, Affinity would rasterise the layer for him automatically.

So far 2.4 beta has resolved this problem pretty well! So glad to see this important bug fixed!

Thanks Dan,
I was copy pasting the ID and password from a site provided by my organisation - so it shouldn't be a spelling mistake - though- the licence key I was copying does have dashes in it. After a clean uninstall and deletion of all the user profile leftovers I was able to reinstall and successfully activate - but I did also take the dashes out of the licence key. (I had tried taking the dashes out before - but that didn't seem to work without the clean uninstall / re/install.

Learn Affinity Designer with this crash course! Covers a wide range of topics including vector essentials, layers, text, colors, images, design tips, and more! Applies to Affinity Designer V2 on Windows and MacOS. 
 

No problem at all, thanks for confirming that for me - I can verify this is a known issue which is logged with our development team, so I'll be sure to 'bump' this with our devs, to bring this to their attention once again.
I hope this helps

Unfortunately we don't offer an export option to such a file format at this time, which is why we recommend PDF for transferring Affinity files to other apps.
This has been discussed in multiple threads throughout the forums previously, I'd recommend checking out one of the threads below -
You can find even more similar threads through a related Google search - 
https://www.google.com/search?q=site%3Aforum.affinity.serif.com+Publisher+to+InDesign
I hope this clears things up!

There's a known issue with Sonoma and time zones. Serif has it on their list but it may be something Apple has to fix.
 

Hi All,
We have now added a new function to permanently set the bounding box to whatever you have cycled it to in the 2.4 beta which is available to try now...
 

Just to confirm, this is how the Anchor panel displays the listed entries in 2.4, returning the previous text colours:


We hope to be able to release this 2.4 beta publicly shortly

Doesn't happen on old macOS versions like El Capitan. - Probably under Sonoma the help window is in your case then in some sort of "modal state", so until closed nothing on a batch panel can be accessed.

Thanks for your report @Stasi!
I can confirm I've been able to replicate this issue within 2.3.1 - it appears to only occur when developing to 32bit RGB output.
If you open Edit > Settings > Assistant > Develop Assistant and change this to 16bit, then redevelop the image, you should find it no longer appears:

I agree this above issue is related, as I've also tested using your RAW file within our currently unreleased internal 2.4 beta and this appears to be fixed already, using either 16bit or 32bit developing.
Therefore once this 2.4 beta version is available, you should find this issue no longer occurs with any Develop Assistant settings!
I hope this helps

Thanks for your report @Wayne Liu!
I can confirm that I have been able to replicate this issue in both Affinity 1.10.8 and 2.3, indicating the issue has likely been present for a while, but requires such a specific workflow to trigger that it has not been identified before this time.
As you've found, using the direct menu option does not seem to cause this - however I will still be logging this as a bug with our development team for further investigating, as it's possible other such dialogs are affected.
I hope this helps

Thanks for your report @Tokamak & our apologies for the delayed response here!
There appears to be a few issues here, mostly stemming from the aforementioned issue (AF-1628), whereby the regular Rectangle and Rounded Rectangle Quick Shapes are sharing properties/default settings, which is likely causing the confusion in your workflow.
Secondly, with the Rounded Rectangle Quick Shape selected, but without drawing this Quick Shape on your document, the Absolute Size slider appears to incorrectly max out at 8mm. If you have a default set with a larger Absolute value, then this will be incorrectly reported on the Context Toolbar without a shape being drawn/selected.
Finally, the Tool Name in the far left of the Context Toolbar is incorrect with the Quick Shape Tool active, but correct with the Move Tool active.
I'm getting these logged with our development team now also.
Do note that if you have a Rounded Rectangle already selected on the canvas, the currently shown values will be repeated for the next Rectangle drawn - if you want to use your default saved values, you'll need to ensure you don't already have a Rounded Rectangle shape selected.
I hope this helps

Thanks for your report Hangman!
I believe the help is incorrect here, as Garry has mentioned the Ellipse has no contextual values and therefore doesn't require/support Presets - so I'm raising this with the documentation team now.
As I understand it, that's to be expected - as the Rectangle Tool supports customisation which can be saved as a preset

I can confirm that this bug is fixed in 2.3.1 (2217) betas of all three Affinity apps. Thanks, I hope for 2.3.1 customer release versions to be out soon.

Thanks for your report @davidkuri!
I can confirm I've been able to replicate this issue here and I'm getting it logged with our development team now.
I hope this helps

Hi @LOB,
Please see my reply to your other post here

Users keep asking about why Publisher doesn't flow text automatically like other apps. This is because the AutoFlow feature isn't discoverable - the Text Flow Out control must be Shift clicked so new users have to read/watch instructions or seek help.
I never use AutoFlow because it breaks my documents but the suggestions below would address all of these issues.
Add setting for automatic AutoFlow: Most apps have an on/off setting for auto flow and when selected will auto flow text without needing to click a control like Publisher. Those apps can also delete blank pages automatically. Publisher doesn't delete unneeded pages so to keep this simple, I suggest adding an "Automatic AutoFlow" checkbox to settings, selected by default, that would prompt the user to automatically auto flow when text is overset. In a perfect world, the alert would include a "Don't show this again" checkbox that would disable the setting without having to visit settings, to avoid annoying experienced users.
Add setting to limit AutoFlow to master page frames: The current feature is manual so pages are never created accidentally, but if the automatic option was enabled, it could get annoying when you temporarily overset a small text frame while editing an image caption. This is why ID limits the feature by default to primary text frames. Publisher doesn't have a primary frame feature but a similar option to limit it to master page frames would be nice. It should limit it to true master page frames, not to text frames pinned inline in master frames.
Add setting to always add pages at end of story: AutoFlow correctly creates pages at the end of a section instead of at the end of a document which is great for those who use sections. For those who don't and who use separate stories for each "chapter", Publisher really needs an End of Story option because otherwise the new frame will be created at the end of the document, potentially hundreds of pages later. ID offers three options: End of Story, End of Section, and End of Document but Publisher does a great job of automatically choosing End of Section versus Document so I think it only needs a checkbox named "Always add pages at end of story".
Add setting to preserve spreads: You might not want a single page to be added because it will mess up your perfect spreads which is why ID offers its "Preserve Facing-Pages Spreads" option. This option adds full spreads and not single pages and would be a good enhancement for Publisher.
Support multiple stories per page use case: When auto flowing a document page frame, if a single text frame exists on an existing page, AutoFlow will skip that page. This makes it impossible to use AutoFlow for both stories in a side-by-side layout (e.g., a Bible translation). AutoFlow could instead check if the new frame would overlap with an existing frame on the page. If it would overlap, create a new page, but if not, then create the frame on the existing page.
Fix issue with non-master frames created on top of master frames: When auto flowing a document page frame, if a single text frame exists on an existing page, AutoFlow will skip that page. But it will create a frame on an existing page with a large master frame full of text - the end result will never be usable. It would be better if autoflow also checked for text names in master page layers.
Thanks

Thank for the swift reply.
I check this as soon as I'm back behind my mac.
Actually, the problems started when I changed some items in the masterpage(s). I'm not 100% sure, but I think when I replaced the PA logo from a .png with the .afdesign.
Keep you posted.

My apologies for the delayed response here @legmaZen / @Hangman & many thanks for the files / further testing provided!
I can confirm that using these steps, I've been able to reproduce the issue across both Windows & macOS, so I'm getting this logged with our development team now.
Inspecting your files, I cannot see any clear cause or reason for this to fail to load - there are no obvious issues with your file or content, and as Hangman has confirmed above, this continues to occur even after 'recreating' the file using 'Add Pages from File' in a new document.
The 'Recovery File' being offered when attempting to open Chapter 2 during the books loading error may be indictive of the cause for this, although I've not seen this occur previously and cannot currently explain the reason this is offered - I suspect that only our developers will have the possibility of discovering the reasoning behind this, using the debug builds available to them.
I've tried to 'repair' your document/.afbook file using a few techniques, though unfortunately as Hangman has covered above, this continues to occur with any iteration of your file that I create, unless certain chapters/pages are not included.
Therefore unfortunately at this time, I would recommend editing each individual chapter separately, and not within a 'Book' to hopefully avoid this issue.
I'll be sure to update you here, with any further information our developers can provide.
I hope this helps
_____________________________________________________________________
Mes excuses pour la réponse tardive ici @legmaZen / @Hangman et un grand merci pour les fichiers/tests supplémentaires fournis !
Je peux confirmer qu'en suivant ces étapes, j'ai pu reproduire le problème sur Windows et macOS, je le consigne donc maintenant avec notre équipe de développement.
En inspectant vos fichiers, je ne vois aucune cause ou raison claire pour laquelle le chargement échoue - il n'y a pas de problèmes évidents avec votre fichier ou votre contenu, et comme Hangman l'a confirmé ci-dessus, cela continue de se produire même après avoir « recréé » le fichier à l'aide de « Ajouter des pages à partir d'un fichier dans un nouveau document.
Le « fichier de récupération » proposé lors de la tentative d'ouverture du chapitre 2 pendant l'erreur de chargement des livres peut être révélateur de la cause de cela, bien que je n'aie jamais vu cela se produire auparavant et que je ne puisse pas actuellement expliquer la raison pour laquelle cela est proposé - je soupçonne que seulement nos développeurs auront la possibilité de découvrir le raisonnement derrière cela, en utilisant les builds de débogage dont ils disposent.
J'ai essayé de « réparer » votre fichier document/.afbook en utilisant quelques techniques, mais malheureusement, comme Hangman l'a expliqué ci-dessus, cela continue de se produire avec toute itération de votre fichier que je crée, à moins que certains chapitres/pages ne soient pas inclus.
Par conséquent, malheureusement, à l'heure actuelle, je recommanderais d'éditer chaque chapitre séparément, et non dans un « livre » pour, espérons-le, éviter ce problème.
Je ne manquerai pas de vous tenir au courant ici de toute information supplémentaire que nos développeurs peuvent fournir.
J'espère que ça aide

Ah ok good sleuthing, so opacity in gradient FX in objects in art board is the bug.… it’s like the film Inception but for bugs 🐜 

Many thanks for providing that for me and a Happy New Year to you too
I've been able to replicate this issue with your file - it appears to be caused when using Opacity values for the Gradient Overlay FX (specifically the one applied to the Group in your document) when used in conjunction with an Artboard.
I'm getting this logged with our developers now, in the meantime if you delete the Artboard and choose to Keep All Objects, you should find this no longer occurs when exporting!

Hi @jubarbie,
Thanks for your report!
I can confirm I've been able to replicate this issue here and I've logged it with our development team - as it appears to occur for all languages on macOS.
I hope this helps

Just to verify, this is something that has been requested with our developers and is being considering internally for a future Affinity Photo update

Hi @Dan C,
Interesting that you're seeing differing results with some of the same workflows when testing on Windows along with some crashes...
Many thanks for testing and logging and glad the info provided proved helpful...