Steps

I strongly assume that for Affinity. The software I develop is structured that way that all seemingly individual apps are in reality just different views and toolbar sets of the same app. 90% is shared code. Even the mobile version has 80% shared code anf the 20% is just plstform specific GUI binding. I doubt Affinity for iOS doed it otherwise. The only thing here I'm not certain of is if every app conzains the same content and just changes the GUI or if they seperared functions into DLLs and Vector stuff is really excluded this way from Photo as the lib is not contained. @fde101 brought that idea up.

@Chris_K Can you name a few of them please?

They may want the full name for personalized newsletters. I don't kbow what they need it for, but I'm usually okay with it since my mail adress contains my full name anyway. Adresses are only asked on purchasing non-digital goods. Serif does this right: If they don't need my address, they don't ask and so they can't loose it on the next big data leak.

All that happens in the Affinity Store, which is part of the website. None of that can be done in the app.

It was not mentioned in the changelog. So there is no reason to assume it should be fixed in 221.

Yes, I also found that none of the bugs reported by me is fixed, too. Just give it time. As long as it's not mentioned in the changelog there is no reason to assume that they tackled a specific problem. I did a quick test for all my reported bugs yesterday and just added the "1.7.0.221" label to indicate that the new version is still affected. You could do the same with your reports. They solve with each version a lot, but by releasing 2 versions a month we should not expect everything to be fixed in one version.

This reminds me of another guy saying the new beta is more unstable than the last.

@fde101 is right here. There is need for both.

The link in this pinned thread worked for me.

Yes. I thought you wanted to sum up which Affinity app has which main Persona and since there is no Bitmap Persona I wanted it to be correct.

Yes, you got that right except that there is no Bitmap Persona. (Designer has a Pixel Persona.) Photos main Persona is the "Photo Persona" No, unfortunately you will only have access to the other apps main Personas. It makes Designer somewhat unnecessary, but Photo has a lot more Personas like Develop, Luiqify, Tone Mapping you won't have access too. I just hope they will make the other two apps unnecessary by merging all Personas into one app. This is not the plan so far. Of course they can sell access to modules seperate even if it's one app. The software I work on does exactly that: You buy "modules" and pay for that. No, this is what "Edit in Photo" does. This is a loose integration with file hand over and at best a workaround. I'm certain the Personas will work in one tool making it a tight integrated app. This makes Publisher so powerful. What you suggest here IMHO would be a total failure.

Yes, you can buy it and refund it in the first 14 days. They have a money back guarantee. This is not a recommendation to do so. Just the only way and you asked.

I guess it just confuses me that you call it "Publisher Persona", because my tooltip says "Layout Persona". I wondered if you found something new. And of course you need that icon to switch back after you worked in another Persona.

So the thing that was unclear to you in your OP was just that Publisher is for working on layouts. Issue solved.

Except that Photo has more Personas: Liqify, Tone Mapping, Export. But yes, that's what the two of us discussed in the other thread: Let us use all Personas in one tool if we have the licenses so I need only to install Publisher.

Yes, and the same applies to the other two Personas: Photo Persona has APhoto Icon and Vector Persona has the ADesigner Icon. The Layout Persona is the currently active main Persona of Publisher. Do you reference to that?

Where do you find that Publisher Persona? I see three Personas: Layout, Photo & Vector.

1.7.0.221 is the current version.

Please add tags "1.7.0.206" and "1.7.0.221" to the topic.

@emlazo1 Can you pretty please append the crash log as text file instead of pasting it into the post? I have to scroll to infinity on my mobile now. Thank you.

@JFisher Did you have any luck so far reproducing the problem with the file I provided?

@dmirate It's highly likely this problem and @Jon P managed to reproduce it. You may also like to share your document and crashlogs. You find all you need inside this topic.

@noxdiurna Can you add the tags "1.7.0.206" and "1.7.0.221" to indicate both versions as affected by this problem? Thank you.

Thank you for the new update! It installed succesfully over the previous version and my documents (all using master pages quite heavily) are still intact. Keep up the good work!

@Seneca I think @emlazo1 wanted to express that the he find version 206 to be more stable.