![]() Under Allow applications downloaded from choose Anywhere.The second workaround is more convoluted but should work for everyone: This only works if you updated to Mavericks from a previous version of OS X and ran bliss previously. The first is, if you can already run bliss from an existing bliss.dmg file, use the in-app updater to update. In the meantime, there are two workarounds. Nevertheless, we will issue a new release as soon as possible. The trouble is that acquiring Mavericks is problematic as mentioned previously we still don't have broadband into our office (hopefully next week) and Mavericks, being the titanic download it is, is not feasible to install over our current 3G connection. Of course, I'm looking to fix this as soon as possible and release a new build. As not all of these contents are signed in bliss, you get the above error message. OS X Mavericks introduces a new requirement that more of the contents of an application must be signed than before. Code signing is a process by which an application can be verified as being produced by a given developer. The underlying issue is that, previously, only certain files in the bliss.dmg were code signed. If you just want to make it work, see the workaround below. ![]() It only affects Mavericks users, but it's a bug nontheless. ![]() ![]() This is a definite problem in the bliss.dmg file created for OS X users. They report an error message similar to: "bliss" is damaged and can't be opened. Since the release of the latest 20131028 version of bliss, I've had a few reports about problems for OS X Mavericks users. The basic structure of the user interface is similar though, so I'm keeping these old pages around in case they still contain useful information. ![]() This post may contain old screenshots of bliss which has been replaced by a new design. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |