peterkrisztianszabo

This is still in the current release! Please fix it!

I agree, it's time for them to fix everything on currently supported os versions before they they close the door on us with 2.0!

And they announce the bugs that are still in the release so noone who would be bothered by them updates?

1.9.3 and still the same! I wish I knew in advance that this was coming and that time machine is the only way to back up affinity apps bought from MAS. This is not really funny for me...

Yup, their answer was that the ui bugs are only in light mode on prehistoric systems.

No offense, but it's none of my business how busy they are as it was their own decision to double their trouble with windows releases. They also don't care how I pay for their stuff. Or how I fix things as an early mac app store customer if they mess up like with this 1.9 and would like to go back a release. Remember, I'm the guy with the broken studiolink because I tried rolling back without time machine to a more bug free version after I upped to 1.9 from 1.8.4 and only had mas saved .pkg files. Staying on topic, there are bunch of places where the buttons are now empty or the text is messed up. If I didn't care about looks I wouldn't be sitting in front of an apple machine. Hey, this bug works in dark mode too! Yay!

Thanks for the actual reply Sean P but I meant by silence that this issue succesfully lived through 1.8.6, 1.9,-1,-2 and not just this long weekend. Seems like it can stay like this with compatibilty ending for yosemite. Thanks for your comment too loukash, I know it's merely a visual thing and this is exactly why it worries me: It should come up in about 30 seconds if the bright ui is tested yet it came out and stayed like this for months. Signaling that even though the app still supports yosemite on paper it's not that much, if at all tested on these systems. I hope that by the time we get to 1.9.8 all things will be fixed.

Thanks for answering. Appreciate the silence.

I can see it from the tag that it's been reported before 1.9 last november. I used 1.8.4 and haven't seen this till 1.9. Could you guys actually fix it? Or is it a low level thing because it only happens on older systems? It is still supported by the app though.

This has been present since 1.9 in all 3 apps. The button label color is not set correctly. It's there, just white! Please fix it! Do I need to create 2 more topics for photo and publisher?

Same thing happens. Thanks for the effort though. To my knowledge there is no apple approved method to reinstall older versions of MAS apps. Which is laughable considering the fact the ios store has every version of an app ever posted by it's dev so I think is a safe bet that The MAS is the same. (This is a fact, I also used this charles proxy trick to get back and old game's .ipa) Meanwhile I've been requested to grab the log of what is going on and seems like publisher is either looking for a product key (serif store) or a MAS receipt but since the .pkg reinstall doesn't create a receipt it ignores the otherwise present ap/ad apps. Lovely. Can the App store be forced via Terminal to reinstall from local source? Like how itunes can be forced to reinstall ios from a downloaded .ipsw file? Can someone confirm that an installed and working affinity suite remains functional if it's restored from a time machine backup when erase the hd and restore a time machine backup with disk utility? This in theory should save everything (the dreaded MAS receipt too).

Hi everyone! -I only ever used to time machine to create a single image snapshot of my fresh/clean systems to restore with disk utility. This process is kind of a reset button. I rarely have to go to such lenghts: last time I used it the GPU of my mbp was replaced (yes, seriously) and before I handed over my mac I removed all my stuff via target disk mode and left a blank system for the time of the repair and restored my backup after I got the mac back. I never reached back to grab a deleted file with time machine. The MAS install does NOT create the files and folders I screen grabbed and posted earlier. I kept those folder open during the MAS install and nothing was created until I actually launched the app. I suspect that the affinity bundle only check with MAS if another app is installed or not meaning if the installation happened any other way (app grabbed from the "past", installed from .pkg) there will be no MAS ticket of it and Publisher will start nagging about the broken Studiolink instead of actually letting users point it to the other installed apps like we do with plugins. -MAS always grabs the full installer if it can't find the app in Applications. Once I didn't delete them and it only grabbed a smaller delta update installer, which alone didn't install a thing as it only contained the diff between the installed and the new version (obviously). If the above is truth, then how does an affinity store publisher link to MAS photo and designer or the other way around? I tried to be cooperative here to solve this and I honestly don't think I caused this. I made my purchases at the time with the best intention: to support the development early but now I feel like I've been shot in the foot.

I'm speechless, as an early adopter I bought the first two when they were only available at the MAS and now I had to fight half a day testing out variations only to find out that there is no way to do this other than ! maybe ! with time machine. And I'm not even sure about that as replacing the 1.9.1 MAS version with it's saved version failed as well. So it fails even if there was no rolling back. Maybe if I restore a single time machine backup with disk utility. Would that work? I certainly see this as defect of the method chosen by the devs. Instead of the buy button there should be "link designer/photo" option. Why is Publisher asking the app store instead of looking around or giving a user an option to point to the apps like with plugins? Restoring an entire system to roll back one app is a total overkill if it even works. I would also like to know why is 10.9 and 10.10 is still supported if testing doesn't go to the lengths of pressing command+N? As "Old Bruce" suggested I could just click the white text on white button version but I'm more concerned about what else could be broken if this is still like this after the release log of 1.9.1 stated that it was fixed. Of course this would be an easy fix if I had an affinity version which was not available when I bought the first two. And looking around here there is no way to switch. I'm sorry but this leaves me with a sour taste.

I'll try to be short: Macbook pro, mac mini, both on 10.10.5 same apps on both, nothing updated other than waterfox classic, the browser. No sync or shared backup, no icloud. I bought all apps from MAS and quickly realized that I need a better affinity backup solution then time machine. I just wanted to save the installers, so I started to grab the .pkg files that the MAS downloads but deletes later. If I prefer to I can roll back a version. Or at least I could have for a while. Turns out studiolink is broken if the app is installed from the saved .pkg file. In this case the MAS doesn't even see the installed apps on the purcahsed tab. No matter which version I install from .pkg, it's broken, even if I haven't removed any other file than the actual app from the applications folder. 1.9.1 is ok installed from the MAS but if the app is deleted and reinstalled from the freshly saved .pkg: it's broken. So there is nothing shared between the two machines just same thing happens: A new version comes out, I delete the old apps from applications but normally nothing else (this is needed to get a full installer and not a delta) and download and saved the new .pkg. Till now the problem didn't show because I never needed to roll back. 1.9 greeted me with a fell apart black and white new doc panel...this started the roll back craze. Btw the apps start for me with the same speed on all versions I tried during this investigation (1.7.3, 1.8.4 and the current ones), do I don't have the slow start problem. I would save a time machine image with a working studio link but at this point the "new file" ui panel is still broken if the light theme is selected. Maybe with 1.9.2 it gets fixed. See pic! I would be happier with 1.8.4, as it seems 1.9 is not really being tested to work with yosemite anymore. Any ideas from devs how to link the apps manually? How does the affinity store version solve this? Too bad the only option was MAS when I bought the firs two apps.

Sorry, had a busy day. Will get back to you once I tried the 1.9.1 builds. There is still no good answer to why is this function also dead on my other mac where I never removed the files. I'm fine with the terminal, as long as you tell me what to type in. I use the console to figure out running times and whatnot.