2.1 macOS App Names Changed?

[Walter Rowe]

Inside Capture One when I use "Open With" or "Edit With" I now see these names for the Affinity apps. They all have "Affinity Store" added to the end of the names. V2, prior to V2.1, they did not have "Affinity Store" in their names.

I looked inside each app's package folder. Their Info.plist names these executables and their MacOS folders have binaries by these names.

In /Applications/Affinity Designer 2/Contents/Info.plist

• <key>CFBundleExecutable</key>
• <string>Affinity Designer 2 Affinity Store</string>

In /Applications/Affinity Designer 2/Contents/MacOS/

• Affinity Designer 2 Affinity Store

In /Applications/Affinity Photo 2/Contents/Info.plist

• <key>CFBundleExecutable</key>
• <string>Affinity Photo 2 Affinity Store</string>

In /Applications/Affinity Photo 2/Contents/MacOS/

• Affinity Photo 2 Affinity Store

In /Applications/Affinity Publisher 2/Contents/Info.plist

• <key>CFBundleExecutable</key>
• <string>Affinity Publisher 2 Affinity Store</string>

In /Applications/Affinity Publisher 2/Contents/MacOS/

• Affinity Publisher 2 Affinity Store

 

I purchased the V2 bundle directly from the Serif Affinity store when it was announced.

Is this a change Serif has made to differentiate the direct sales binaries from the Mac App Store binaries?

[Patrick Connor]

Thanks for pointing this out.

We have recently automated one of our build processes, and we build for the Affinity Store and the Mac App Store from the same codebase. I think this was a consequence of that change, but I think it is a harmless change, and does help distinguish the 2 versions for us internally. I will check with the Devs if this is an accidental change, as I must admit I am not 100% sure.

[Return]

24 minutes ago, Patrick Connor said:

Thanks for pointing this out.

We have recently automated one of our build processes, and we build for the Affinity Store and the Mac App Store from the same codebase. I think this was a consequence of that change, but I think it is a harmless change, and does help distinguish the 2 versions for us internally. I will check with the Devs if this is an accidental change, as I must admit I am not 100% sure.

Perhaps this could also be an option for windows?
aka windows store vs affinity store vs msi versioning.
Meaning running different versions in beta makes it more distinct.

[walt.farrell]

3 minutes ago, Return said:

Perhaps this could also be an option for windows?
aka windows store vs affinitytstore vs msi versioning.
Meaning running different versions in beta makes it more distinct.

Yes, that could be helpful.

[Walter Rowe]

On 5/23/2023 at 8:22 AM, Patrick Connor said:

Thanks for pointing this out.

We have recently automated one of our build processes, and we build for the Affinity Store and the Mac App Store from the same codebase. I think this was a consequence of that change, but I think it is a harmless change, and does help distinguish the 2 versions for us internally. I will check with the Devs if this is an accidental change, as I must admit I am not 100% sure.

Another mac user also experienced this. They said the downloaded the full 2.1 suite again (vs using the in-app upgrade) and the apps were named as expected. I plan to try this myself.

[Walter Rowe]

Freshly downloading V2.1 packages did not change the app names. They still include "Affinity Store" in the name.