ericosmosNEW

It says something like “resources missing. Relocate. Replace. Cancel.” If I remember correctly. When I go choose “relocate” it opens the correct folder where all my resources are. Then the only thing I can do is click on one of the files. Then the tab closes and nothing has changed.
The files are in a folder on my iPad.
I remember Affinity having some authorisation issues with folders on iOS systems. Might be related.

A little bit, yes. It basically creates new nodes where the overlap doesn't match perfectly,  but it can easily be deleted again. And it is relatively fast

Exactly

Thx for clarifying. Installing all used fonts (of the Designer files) on the local machine fixed it instantly.
But being able to include "linked-linked" data into a package file would certainly be a worklow improvement.

When you clip the mesh warp group to the curve, the visible extent of the group is determined by the containing curve, but the invisible parts are merely hidden rather than being removed. If you use the curve to mask (or crop) the mesh warp group, you are cutting off the parts of the group that lie outside the containing curve, albeit non-destructively. The difference is particularly noticeable with the 3D Effect: a masked/cropped object will have the effect applied after masking/cropping, making the effect visible all around the object; a clipped object, on the other hand, will have the effect applied to the original object, so some of the 3D edge will be obscured by the clipview window.

You're welcome.

I appreciate the further testing you've conducted - as it appears you have determined the cause of this error, and I can verify it's a bug.
I can confirm that you should be able to drag and drop a layer into a Picture Frame, for the layer to become the frame contents - rather than simply a nested child layer like other objects in Affinity.
In Publisher on Desktop, you can drag and drop an image into a frame using the Layers Studio, regardless of the current layer selection:
2024-02-08 16-47-30.mp4  
However in Publisher on iPad, it appears as though you need the Picture Frame Layer selected, in order for the object to correctly be adopted as the frames contents. 
If you have the image layer selected, or a different layer when drag-dropping the image, it may result in the object being added as a regular Child layer to the frame, causing the behaviour you're seeing:
RPReplay_Final1707412031.MP4
I don't believe this difference is expected behaviour and therefore I'm logging this with our developers now. In the meantime please ensure you see the 'Picture Frame' icon in the thumbnail for the Image layer within the Picture Frame, to confirm that it has correctly been added as the Frame contents layer.
I hope this helps

I can understand that it may not be desirable to have a change you make in Publisher of a linked Designer file also alter the original Designer file. But not even Publisher keeps the change!  As of now, changing Designer files within Publisher is basically pointless 🤷‍♂️
 
FullSizeRender.MOV

relieving to know!
Just to add, if you change the linked Designer file in Designer and save it, it will be updated in Publisher. (There is a red exclamation point in the lower right bar. When you click it, it shows all the Designer files that have been altered and asks you to "correct" -> meaning update it by tabbing it) This way around it works

I’ve placed Designer files in a Publisher document (as linked), so I can still make all sorts of changes when double clicking on the Designer file. But for some reason Publisher cannot keep the changes. Even after saving the Publisher file, going back in the changed placed Designer file has lost the changes.
And another maybe related question: how can I make changes in a placed Designer file in Publisher and have those changes also realized in the original Designer file? So when I open the file in Designer the change is also there?

uhhh... that looks bad.
I must have been lucky that my changes of a Designer file within Publisher just weren't saved instead of getting corrupted completely.

Ah, yes. Thank you!
The infamous long-press function 😅

Copy it, then return to the Home Screen, long-press on new, and use New from  Clipboard.

Long press… what the hell. 🤪
Wow, I don’t understand the UX reason on that one, first instinct is to tap screen not long press.
I would had never guessed that one, thank you BIG TIME!  

Sorry; I missed that this is an iPad question.

I'm having this same problem! It's so hard to describe and I'm glad that others were able to explain and get some visual proof. Is there any kind of update on when this fix will be delivered? Changing resolution or file size is not an option. I love affinity and love that I can work between the iPad and desktop versions however if this continues to be a problem I simply can't continue with affinity photo. I lose too much work and it's too unpredictable.

The group can also be moved or scaled afterwards.

Does my attached video help?
Remember to put the ‘hexagon curves’ above the ‘text curves’ before using the Intersect operation.
2022-10-14 09-29-28.mp4

It's been a while since I've posted anything here. Just curious what the status is for address this particular bug. Reinstalling didn't last long before the problem came back for me.
Thanks

The file, opened in Photo and using the channels panels, shows some areas with alpha below 1, especially in the defect area, but elsewhere, too.
You can achieve full alpha by channels panel, right-click on pixel layer alpha, and fill. Unfortunately the color information is still lost in the affected area. Damage is permanent unfortunately.
 
So it is not a rendering issue, but a more severe damage.
The thumbnail probably showed cached information just before the issue hit, not the actual pixel layer data.
 
PS: the symptoms remind me more on this bug known from iPad OS:
 

Apologies for the delayed response,
You can reduce the DPI of your document, without changing the physical dimensions - which should allow for physically larger canvas/layer sizes, before hitting the vRAM limit
There is a difference between 'RAM' and 'vRAM' - RAM is the memory that your CPU has access to for volatile data, vRAM is the memory that the GPU has access to, and it's when the vRAM limit is hit that is issue occurs, not the RAM limit.
I hope this helps!

Hey @ericosmosNEW, I'm sorry that you're having the same issue. It's good to know they've identified the cause, now we just have to hope it won't take years for this to be fixed...

Hey, just want to let you know, you are not alone. I have this bug using Affinity Photo for iPad Pro and have brought this issue to Dan’s attention as well. My way of working triggers this bug in virtually every file I work on.
Hey @Dan C any news on the horizon regarding this? It has been a while…

Yes, that’s exactly what I was looking for. Thank you!
I finally know what this intersect mode is for 😊👍

Think different. Instead of subtracting all other colors, use flood selection tool set to mode “intersect”, and click once on the desired color. Should do the job.