Beta build 2.2 (03) 1931 is installing into the live active version 2.1.1

[StuartRc]

Hi😀
I tried to update beta build 2 to beta build 3 but the update wants to install on the live 2.1.1 version (It has done so for 2.1 AD as it was open!) I have declined with Photo 2.1 and Publisher 2.1

 

[Sean P]

Thanks StuartRc,

We're aware of this and will be removing it very shortly. 

Thanks again for making us aware!

[StuartRc]

5 minutes ago, Sean P said:

Thanks StuartRc,

We're aware of this and will be removing it very shortly. 

Thanks again for making us aware!

No problem!...it did make me laugh this morning...I will replace it with correct version! 😀

[Sean P]

Just now, StuartRc said:

No problem!...it did make me laugh this morning...I will replace it with correct version! 😀

Providing you haven't upgraded, can you go into C:\ProgramData\Affinity\appname\2.0\ and delete the files inside there please. When you launch the app it shouldn't prompt you again

[b.kaas]

Hi,

I am working whith a partner on a some 150 pages project. We share files by cloud. A few hours ago I was asked to update to 2.2. I can not remember it said "beta". And now there is only the 2.2 Version running on my desktop.

My partner wasn'n asked. But now he ist not able to open the file I have been working on. This is an actual problem now.

Does he have to join the beta-program? (he does not intend to yet ...) Or can I go back to 2.1?

Thanks to anybody with some help!

Bernhard

 

 

[StuartRc]

Hi

I accidentally installed beta 2.2 over 2.1.1 I am not surprised you have file issues!
Then
I just un-installed it and replaced with previous version from account. Works but after a while it repeated the request to update. So I followed Seans instruction above and deleted the files.. seems ok now!

[Sean P]

1 hour ago, b.kaas said:

Hi,

I am working whith a partner on a some 150 pages project. We share files by cloud. A few hours ago I was asked to update to 2.2. I can not remember it said "beta". And now there is only the 2.2 Version running on my desktop.

My partner wasn'n asked. But now he ist not able to open the file I have been working on. This is an actual problem now.

Does he have to join the beta-program? (he does not intend to yet ...) Or can I go back to 2.1?

Thanks to anybody with some help!

Bernhard

 

 

Hi Bernhard,

Firstly please accept my apologies for this. Unfortunately due to changes in the app the files do unfortunately become incompatible in older versions when saved in a newer version (i.e 2.1 cannot read 2.2 saved files).

In this instance unfortunately you will both need to work in the beta version to be able to use the file. Please see the link below for how to do this. Due to file and feature serialisation it is not possible to roll a file back once saved. However your cloud service may keep backups of the file (I believe Dropbox does), so you might be able to rollback the file to a slightly earlier 2.1 saved version, allowing you to both work from the 2.1 retail build.

I would still suggest you uninstall the 2.2 retail and redownload and reinstall the 2.1 version from your account, however.

Again please accept my sincere apologies regarding this. 

 

 

[b.kaas]

Thanks StuartRc and Sean P!

I turned back to 2.1. We are now working with a backup file. Fortunately not much work ist lost.

 

Edited August 2, 2023 by b.kaas

[Patrick Connor]

We are still investigating. 

[ctekk]

On 8/3/2023 at 3:12 AM, Red Sands said:

Whooooa! Am I reading that right?

So how many customers have updated their production environment to a pure test version with changes to something as critical as how files are saved and in a format that cannot be opened by anyone other than beta versions? You must have logs.

This is a major incident that can't just be rolled back and left for customers to discover and mitigate!

3 million customers? Then you need to communicate and do some damage control!

At least 1 (me)  

[Bryan Rieger]

On 8/2/2023 at 9:12 PM, Red Sands said:

So how many customers have updated their production environment to a pure test version with changes to something as critical as how files are saved and in a format that cannot be opened by anyone other than beta versions? You must have logs.

This is a major incident that can't just be rolled back and left for customers to discover and mitigate!

3 million customers? Then you need to communicate and do some damage control!

This is exactly why I never touch the betas anymore.
Sure, 99% of the time they run completely isolated from release versions, but that 1% of the time can quickly become a very costly mistake.

That, and the countless times I've accidentally opened—and saved—a working file in a beta app without realizing it until it was too late, only to be locked out from opening the files in the stable release version.

Honestly, some form of backwards compatability with the Affinity file format is becoming increasingly necessary. Even the ability to back save it to a prior version would be a huge help, and I'm sure most folks would be willing to lose a few new features they may (or may not) be using in the beta or latest release(s) in order to be able to revert, share, and collaborate with others who may be running a different version of the software.

[Bryan Rieger]

22 minutes ago, Red Sands said:

Yes, but it's a personal choice, and that's how things are as a tester. I generally agree about file compatibility, but I can keep production data and test programs separate myself. You have to even if there is full file compatibility. I'm also quite experienced in this from my work, where I often have access to beta and test versions, so I am very aware of what I do and when I run the Affinity beta.

Yes, as someone accustomed to regularly working professionally with, and testing early prototypes, alphas, and betas you quickly learn to isolate test environments and data to ensure you're seeing what you think you're seeing, and also to limit any possibility of corruption. The thing is, many users now running public betas don't always have this rigorous process and assume the betas have been extensively tested and are generally stable pre-releases. Accidents will happen, and if you haven't isolated everything properly problems will arise.

While there are a number of folks in these forums with extensive software development experience, not all users running the betas will have that experience, and many will lack the knowledge of how to properly work with beta software to avoid data corruption issues. Of course all of this is covered in the Affinity Beta Software Program:

Quote

The Affinity Beta Software Program lets users try out pre-release software. The feedback you provide on quality and usability helps us identify issues, fix them and make Affinity apps even better. However, since the beta software has not yet been commercially released, it may contain errors, have stability issues and generally may not function as well as our retail versions. For this reason, we would not advise using the beta versions for important production work. Please also consider that documents saved in the beta versions may not be backward compatible with the currently released version.

"…would not advise using the beta versions for important production work." This probably needs to be much clearer, especially when opening files in a beta app.

"…documents saved in the beta versions may not be backward compatible with the currently released version." This seems to be true 99% of the time. It's probably safer to inform users that any documents opened and saved in a beta app will not be compatible with earlier release versions—even with a x.x.1 release.

[walt.farrell]

49 minutes ago, Bryan Rieger said:

That, and the countless times I've accidentally opened—and saved—a working file in a beta app without realizing it until it was too late, only to be locked out from opening the files in the stable release version.

The beta apps in V1 and now in V2 warn you if you open a non-beta file, so there should be no reason for not realizing this. 

The initial beta for V2 was missing that warning, but that's been fixed a long time ago.

[Bryan Rieger]

Just now, walt.farrell said:

The beta apps in V1 and now in V2 warn you if you open a non-beta file, so there should be no reason for not realizing this. 

The initial beta for V2 was missing that warning, but that's been fixed a long time ago.

I haven't touched the betas in ages, so I'll take your word for it. Glad to see the betas do that now.

[walt.farrell]

1 minute ago, Bryan Rieger said:

documents saved in the beta versions may not be backward compatible with the currently released version." This seems to be true 99% of the time. It's probably safer to inform users that any documents opened and saved in a beta app will no be compatible with earlier release versions. This even being true for a x.x.1 release

It depends on whether it's a beta for 2.x where the files will not be compatible with an earlier x, or whether it's a beta for 2.x.y, where the files will still be compatible. 

When I mentioned that, Serif said they wanted a single message, and for that "may" is accurate. But perhaps they should go further and explain the details.

[Patrick Connor]

16 hours ago, Red Sands said:

...impact is serious.

We agree and files created using this build will be fully supported.

[anto]

Please add a warning window if files are opened in incompatible versions. I have the beta version installed, all the file shortcuts of the Publisher on Windows show beta icons. And double click they open in beta version. Files created in version 2.1 are opened and do not report that they are incompatible with the beta version 2.2.
My topic was ignored again. This is a big problem.