nwhit

Not sure if this is related, but I just had with APub rc2 a couple freezes on quit. In the first case, there was an unsaved/untitled file and it froze (spinning beach ball) when trying to click the Save. I then reopened, opened the recovery file, saved that, then tried to quit. Again, freeze with beachball. Had to force quit both times. 
Interestingly, both times I got the dialog to notify Apple about the crashes, but in Console there were no crash reports. The only thing there is under Diagnostic Reports for the same time as one of the crashes, or perhaps the restart. Attached JIC. 
UPDATE: When I Revealed in Finder the diagnostic report, I did see 2 "Hang" reports for APub, so have attched those as well.
Affinity Publisher 2 Beta_2023-05-13-181151_TRAC-Main20.hang Affinity Publisher 2 Beta_2023-05-13-181329_TRAC-Main20.wakeups_resource.diag Affinity Publisher 2 Beta_2023-05-13-181359_TRAC-Main20.hang

Thank you both! I have now replicated this and passed it onto development.

@nwhit
Yes, that's right. They would download a trial from the Apple Store and then pay Apple as in app purchase from within the free trial.

Thanks!
UPDATE: Yes, noticing that I lose the visibility buttons every time I quit the apps. Requires dragging the pane out of the docked position, then dragging it back into the dock. 

When first launching the new betas and using them for awhile, all three apps had the Layers visibility buttons gone. Stayed that way through quits and reopens. Found that I had to remove the Layers pane from the right-column docked position. The buttons then showed and I could then move the pane back into the docked position. 
Very minor issue but might have someone confused when they open v2.1.1732 apps. 

Affirm that Photo does not import the plugins pref, and all apps didn't import the Toolbar pref for Icon & Text.
But THANK YOU, THANK YOU for importing the actual Studio layout from the working versions! That has always been such a PITA having to rest those up. 

Affirm that Photo does not import the plugins pref, and all apps didn't import the Toolbar pref for Icon & Text.
But THANK YOU, THANK YOU for importing the actual Studio layout from the working versions! That has always been such a PITA having to rest those up. 

Apps: Publisher
Platforms: Windows, macOS and iPad
With a picture frame selected, pasting inside will now insert your clipboard contents to be held within the picture frame rather than being clipped by it. Also if you have your insertion target set to inside and you paste normally with a picture frame selected the same will happen.

Apps: Photo
Platforms: Windows, macOS and iPad
A number of improvements have been made to the crop tool based on customer feedback:
Crop to selection. If you have a pixel selection active the crop tool will now initiate to be a min fit around the selection you have. After a crop the current zoom level will be maintained (rather than automatically zooming to fit as previously). From various feedback this was considered preferable behaviour and leaving it to the user to choose if they want to zoom to fit after (cmd-0 or hitting zoom icon in the top toolbar of iPad). The Crop tool now remembers the last setting globally, so if you wish to apply the same ratio crop to a number of images it's much easier. You can now drag anywhere on the bounding box edges to resize the crop, rather than having to drag from a handle. Enter as well as Return will now commit a crop Escape will reset the current crop In unconstrained mode, holding Shift will constrain the current aspect ratio and Cmd (Ctrl on Windows) will resize around the centre When you rotate / use straighten feature in crop tool it will now automatically adjust crop box to fit. Please let us know what you think or if you spot any issues or have any feedback on this new behaviour.

Apps: All
Platforms: Windows and macOS
For the convenience of Beta testers we have add an option in preferences to migrate all settings and content you have in your retail versions over the beta versions at anytime. You can find this under the beta menu of preferences.

Yes, agreed. A different issue to images from the Stock pane, but a similar idea. When the web image linking feature first came out, I tried it but, as you said, made me cringe at the thought that an asset within a document wasn't someplace safe (other than if it were on one of my own websites, but even then...).
I just believe that to make using images from the Stock pane safe and user-friendly, they really should either be automatically embedded, or the user should be given the immediate choice of downloading it to a safe place where it can be linked, if desired to have it linked. Mysteriously and "secretly" downloading it to some temp directory doesn't seem wise or prudent at all. 

Yes, I remember testing that new feature. The more I think about this issue, the more I think there needs to be a better solution to adding stock images. Be VERY nice to be able to drag-and-drop the image, but have a pop-up to save the image to the local drive and use as linked. When I lost the couple of hard-to-find vector images in this current doc, it did take me awhile to re-locate them in Pixalbay, then I had to go through the document to find each instance and replace the "missing" versions with the new embedded versions (I manually changed them immediately to embedded after re-adding them). I'm guessing 98% of users might never know their dragged-and-dropped stock images could disappear/go missing on them! 

Okay, after a whole bunch of searches and reading, finally found an answer in a beta thread. 
1. In Preflight panel, need to click the Edit Profile in the little Actions menu (top right of pane).
2. Go down to PDF Passthrough, then select the minimum type of PDF you're wanting to Place.
3. Will need to Create a Preset for that setting since the Default seems to be a minimum of X-1a:2003. Otherwise you will always see the error message if you are Placing regular v1.7 PDFs. 
Overall, doesn't seem like a very intuitive or smooth way to do this preflighting. Would think there would be a better way, but who knows. Maybe in upcoming versions.
Just wish that this would be explained on the need and how to do this in the online Help for the app! The Help says there is a Preflight for PDF Passthrough, but doesn't explain how it works and the need to set it to what you want in the Edit mode. 

The "solutions" have already been, very fairly, explained.
If you just recently bought V1, Affinity has provided an email address to submit for possible resolution. If you bought so-so recently, and aren't ready to pay for the new version, don't upgrade. No one has to upgrade. Use v1 for a few more months or a year or so to amortize the cost over a longer period. V1 runs, produces massive amounts of pro-level media for our company's clients, and will keep running for the foreseeable future. Then later when you feel you've gotten enough "use" out of V1, then buy the new V2 version. That said, as been the history with Affinity, they are truly giving this fantastic software away at a very, very, very competitive price, whether at full retail or right now at the introductory price. Just seems strange that people are somehow construing that Serif are somehow forcing people to upgrade just because they launched a new version. If you don't want to pay the price, don't upgrade. Keep using V1 apps. They're great. 

We don't know that for certain, we only have Serifs records to hand. Other purchases may have been made on other Apple or Microsoft stores, but we have No Record of any of those, which is my point about being unable to be fair to offer differential prices to ALL existing customers without making thousands of mistakes and upsetting everyone. A single offer price is pretty much the only easy way to do this launch and I'm sorry that each person who thinks they should have been offered something else cannot see that all other solutions present different problems 

A 10-minute free download would answer your question quite quickly. But OTOH, I found over the many, many months when Affinity was developing the IDML import in numerous betas, that any time my company came across an IDML import problem, it was very easy to upload it to their tech staff for evaluation and troubleshooting, which always resolved the problem, sometimes albeit after an upgrade. There are, of course, many things that can be done in ID that don't export well, much less import properly, but Affinity staff has been relentless in working on those issues to get them resolved, assuming they can be resolved. Sometimes it is the fault of ID, not Affinity that causes the import problem.
May not be the answer you're looking for but it is a viable path.

Thanks Ash, I think this is exactly what we all wanted to hear!

Hi All,
Well, it’s been a pretty crazy week since the launch of V2!
This has been a real labour of love for us over the last year or so, and I can’t even begin to describe how hard the development team have worked on it. Not only getting the V2 apps launched, but also of course finally bringing Publisher to iPad. 
With this being our first paid-for upgrade there has understandably been a lot of feedback / questions around future updates and our pricing policies. I thought it was worth addressing / clarifying our position on some of these personally...
Updates to V2 moving forward
Buying V2 not only gets you all the new features you have seen, but we have various updates planned – including many more new features and improvements – which you will get for free. This will continue until such a time that V3 is released. We’re not sure exactly when V3 will be, but I can confirm we are not going to move to anything as regular as an annual upgrade cycle as has been speculated.
It’s worth saying too that V2 does include many under-the-hood changes to our underlying technology, and we have also been investing in several new areas of research recently. Some of these haven’t manifested themselves into new features yet, but overall V2 does give us a better platform to develop on moving forward and I’m sure you will be pleased with the updates V2 will receive.
Updates to V1 moving forward
While we did say on the FAQ that V1 would no longer receive any updates, I want to clarify that was about new feature updates. We will be updating V1 to fix any critical problems caused by operating system updates in the future. So if the next version of macOS breaks V1 we will endeavour to fix it. There will be a point in time when continuing to maintain V1 in this way will not be tenable, but certainly for the foreseeable future we will continue to patch. In fact, we have an update to V1 queued up for release very shortly with some fixes for Ventura and issues caused by a recent Windows security / quality update. 
We will update our FAQ shortly to make that clearer for everyone.
Offer period
In case you didn’t see, I’m pleased to confirm we have decided to run this initial launch offer until 14th December to give everyone the best chance possible to get it if they wish / have a decent amount of time to trial it. 
Upgrade pricing
It’s been really hard to see some of the comments about us not looking after our existing customers – we’re pretty devasted that anyone feels like that to be honest. But the fact is we felt our hands were tied somewhat with being able to offer upgrade pricing in a fair way. The main reason for this was App Store customers (which make up around 35% of our userbase). The problems with that are two-fold: firstly, we didn’t have a way from within V1 to validate an App Store purchase receipt to reliably ensure customers who were entitled to an upgrade could get one; and secondly, we could not find a good way for people to get that discount via the App Store. Us pushing upgrade customers to go exclusively via our own site (including customers who were previously acquired via the app stores) may also have put us in violation of App Store Ts & Cs which we were obviously concerned about.
I’m not saying that these issues were completely insurmountable, but any solutions we came up with would be messy, and most importantly could have resulted in some bona fide V1 customers struggling to get validated and claim their discount. We certainly don’t have the support resource here if we ended up needing to manually validate tens of thousands of receipts for example.
The only option we felt was safe to move forward with was a general launch offer, which would guarantee that every V1 customer could get the discount, whether they purchased directly through us or the App Stores. We knew a side effect of that would mean some new customers would end up receiving that same discount – but we felt that was a better option than V1 customers missing out. It’s also worth saying that while there has been some good press about V2, all our main marketing has been via email and through social media to our followers. In other words, we felt ok about it because we knew the vast majority of people who would find out about it or take advantage of the offer would be existing customers. I would be surprised if over the offer period customers upgrading from V1 didn’t make up more than 90% of our sales.
Overall I do believe us giving a 40% discount, along with the addition of the new Universal Licence of course, is offering fantastic value for money for those who want to upgrade. 
However, taking on board some of the feedback there is something extra we can do – we will offer a new free bundle of content exclusively for V1 customers upgrading to V2 as an extra thank you for your support. I’ve seen this suggested by a number of customers and it’s a great idea as it does remove the App Store conflict entirely. 
We’ll need a little time to put something together, but all customers who previously registered or purchased V1 and have since upgraded to V2 will receive a voucher code for this via email as soon as we can.
A comment on no subscription
I do want to say that some of the points above are exactly the reason why software companies move to subscription. Whatever you do with upgrade pricing, you still have the issue of customers who bought the previous version 3 months ago vs. those who have had it 2+ years. Offering perpetual licences also gives the additional overhead of needing to maintain the previous version longer than you would if everyone was on subscription / generally always on the latest version.
We are a small team so some of these complications are not ideal — all we really want to do is focus on developing our latest codebase, push out regular updates and continue with our mission to make great creative software accessible to everyone. 
But it does need to be funded somehow. We know you love our no-subscription model, but there also needs to be a level of appreciation that the alternative is having paid-for upgrades from time to time. That unfortunately comes with its own problems.
All of that said, I have to say we have been blown away with the response to V2 - around 3 times as many people have upgraded in the last week than we expected - and we really can't thank you enough for the support you have shown. More than anything the success of this upgrade puts us in a great place to continue investing heavily in development which is ultimately what it's all about, and we’re super excited to crack on with some great updates coming next year!
All the best,
Ash

A 10-minute free download would answer your question quite quickly. But OTOH, I found over the many, many months when Affinity was developing the IDML import in numerous betas, that any time my company came across an IDML import problem, it was very easy to upload it to their tech staff for evaluation and troubleshooting, which always resolved the problem, sometimes albeit after an upgrade. There are, of course, many things that can be done in ID that don't export well, much less import properly, but Affinity staff has been relentless in working on those issues to get them resolved, assuming they can be resolved. Sometimes it is the fault of ID, not Affinity that causes the import problem.
May not be the answer you're looking for but it is a viable path.

V2 has a very bright future. It seems the entire core of the software needed to fork to v2 to clear the way for 2.0 roadmap and shed eliminate whatever technical barriers existed in v1.
Considering the complexity of StudioLink, something even Adobe can’t replicate without rewriting 20+ years of legacy code stacked on legacy code across all of their apps, this release is pretty smooth.
Forums are never a reliable indicator of overall satisfaction because happy users are busy working. 
 
 
 

The "solutions" have already been, very fairly, explained.
If you just recently bought V1, Affinity has provided an email address to submit for possible resolution. If you bought so-so recently, and aren't ready to pay for the new version, don't upgrade. No one has to upgrade. Use v1 for a few more months or a year or so to amortize the cost over a longer period. V1 runs, produces massive amounts of pro-level media for our company's clients, and will keep running for the foreseeable future. Then later when you feel you've gotten enough "use" out of V1, then buy the new V2 version. That said, as been the history with Affinity, they are truly giving this fantastic software away at a very, very, very competitive price, whether at full retail or right now at the introductory price. Just seems strange that people are somehow construing that Serif are somehow forcing people to upgrade just because they launched a new version. If you don't want to pay the price, don't upgrade. Keep using V1 apps. They're great. 

The "solutions" have already been, very fairly, explained.
If you just recently bought V1, Affinity has provided an email address to submit for possible resolution. If you bought so-so recently, and aren't ready to pay for the new version, don't upgrade. No one has to upgrade. Use v1 for a few more months or a year or so to amortize the cost over a longer period. V1 runs, produces massive amounts of pro-level media for our company's clients, and will keep running for the foreseeable future. Then later when you feel you've gotten enough "use" out of V1, then buy the new V2 version. That said, as been the history with Affinity, they are truly giving this fantastic software away at a very, very, very competitive price, whether at full retail or right now at the introductory price. Just seems strange that people are somehow construing that Serif are somehow forcing people to upgrade just because they launched a new version. If you don't want to pay the price, don't upgrade. Keep using V1 apps. They're great. 

The "solutions" have already been, very fairly, explained.
If you just recently bought V1, Affinity has provided an email address to submit for possible resolution. If you bought so-so recently, and aren't ready to pay for the new version, don't upgrade. No one has to upgrade. Use v1 for a few more months or a year or so to amortize the cost over a longer period. V1 runs, produces massive amounts of pro-level media for our company's clients, and will keep running for the foreseeable future. Then later when you feel you've gotten enough "use" out of V1, then buy the new V2 version. That said, as been the history with Affinity, they are truly giving this fantastic software away at a very, very, very competitive price, whether at full retail or right now at the introductory price. Just seems strange that people are somehow construing that Serif are somehow forcing people to upgrade just because they launched a new version. If you don't want to pay the price, don't upgrade. Keep using V1 apps. They're great. 

As a media production firm, we've been running CS6 in a Parallels VM (Sierra for max compatibility for a bunch of software) for the last couple years with no real issues. Runs fast, works, shares files with the main OS, etc. Allowed us to upgrade the main host OS for newer software like Affinity. 

The "solutions" have already been, very fairly, explained.
If you just recently bought V1, Affinity has provided an email address to submit for possible resolution. If you bought so-so recently, and aren't ready to pay for the new version, don't upgrade. No one has to upgrade. Use v1 for a few more months or a year or so to amortize the cost over a longer period. V1 runs, produces massive amounts of pro-level media for our company's clients, and will keep running for the foreseeable future. Then later when you feel you've gotten enough "use" out of V1, then buy the new V2 version. That said, as been the history with Affinity, they are truly giving this fantastic software away at a very, very, very competitive price, whether at full retail or right now at the introductory price. Just seems strange that people are somehow construing that Serif are somehow forcing people to upgrade just because they launched a new version. If you don't want to pay the price, don't upgrade. Keep using V1 apps. They're great.