Permalink
Browse files

Changed the ChromeEngine so it still points to "Google Chrome" as its…

… executable instead of ChromeEngine (which is the link we use to actually launch it). This for some reason allows Browser Fairy to work again.
  • Loading branch information...
David Marmor
David Marmor committed Feb 22, 2016
1 parent 37a59e2 commit fe3295441f9d5e95524b154eaebd9f35d27905ba
Showing with 18 additions and 12 deletions.
  1. +6 −8 README.md
  2. +6 −0 app/CHANGELOG.md
  3. +5 −3 app/src/runtime.sh
  4. +1 −1 app/src/version.sh
View
@@ -1,4 +1,4 @@
# Epichrome 2.1.10
# Epichrome 2.1.11
**Epichrome** is made up of two parts: an AppleScript-based Mac application (*Epichrome.app*) and a companion Chrome extension (*Epichrome Helper*). *Epichrome.app* creates Chrome-based site-specific browsers (SSBs) for Mac OSX (Chrome must be installed in order to run them, but they are full Mac apps, each with its own separate Chrome profile).
@@ -13,17 +13,15 @@ Download the binary release [here](https://github.com/dmarmor/osx-chrome-ssb-gui
See [CHANGELOG.md](https://github.com/dmarmor/osx-chrome-ssb-gui/blob/master/CHANGELOG.md "CHANGELOG") for the latest changes.
## New in version 2.1.10.
## New in version 2.1.11.
*Note: This is likely to be my last update for a while (except for fixing catastrophic problems like 2.1.7). My day job has gotten very busy, so I probably won't have time to work on new features or major updates for the foreseeable future.*
*Note: I'm currently only addressing bugs at the moment. My day job has gotten very busy, so I probably won't have time to work on new features or major updates for the foreseeable future.*
**If you're running any previous version, please update to version 2.1.10 as soon as possible. It fixes a potentially serious bug where updates to Chrome could break Epichrome apps permanently, so they'd have to be deleted and recreated.**
**If you're running any version earlier than 2.1.10, please update to the latest version as soon as possible. Prior versions have a potentially serious bug where updates to Chrome could break Epichrome apps permanently, so they'd have to be deleted and recreated.**
This version also fixes a minor bug that would cause apps to display the wrong dock icon if an app was used to download a file or display certain dialog boxes. Thanks to [rschend](https://github.com/rschend "rschend") for finding this and tracking down the cause, and to the others who contributed their reports.
This version fixes a bug that broke compatibility with Browser Fairy (a great app that allows you to route URLs to different browsers based on their origin or the content of the link). For now, links are still not able to launch an Epichrome app (but will route properly if the app is already open). The next update of Browser Fairy should fix that last problem too. Thanks again to [rschend](https://github.com/rschend "rschend") for identifying this, and to [jschuster](https://github.com/jschuster "jschuster"), the creator of Browser Fairy, for helping with the fix!
This version will also fix crashes you may be experiencing since the release (on January 21, 2016) of Chrome 48.0.2564.82, which was breaking all Epichrome apps based on 2.1.7 or earlier. If your apps no longer start, install the latest Epichrome and run them again. Each one should offer you the choice of updating to the latest version, after which they should work again. See [CHANGELOG.md](https://github.com/dmarmor/osx-chrome-ssb-gui/blob/master/CHANGELOG.md "CHANGELOG") for more details.
Thanks to [ylluminate](https://github.com/ylluminate "ylluminate"), [evansthompson](https://github.com/evansthompson "evansthompson"), [msubel](https://github.com/msubel "msubel"), and everyone else who pointed this problem out. Special thanks to [breeden](https://github.com/breeden "breeden") for helping test the solution!
This version will also fix crashes you may be experiencing since the release (on January 21, 2016) of Chrome 48.0.2564.82, which was breaking all Epichrome apps based on 2.1.7 or earlier. If your apps no longer start, install the latest Epichrome and run them again. Each one should offer you the choice of updating to the latest version, after which they should work again. See [CHANGELOG.md](https://github.com/dmarmor/epichrome/blob/master/CHANGELOG.md "CHANGELOG") for more details.
## New in version 2.1
View
@@ -2,6 +2,12 @@
This project adheres to [Semantic Versioning](http://semver.org/).
## [2.1.11] - 2016-02-21
### Fixed
- Fixed a bug that broke compatibility with Browser Fairy. For now, links are still not able to launch an Epichrome app (but will route properly if the app is already open). The next update of Browser Fairy should fix that last problem too. Thanks again to [rschend](https://github.com/rschend "rschend") for identifying this, and to [jschuster](https://github.com/jschuster "jschuster"), the creator of Browser Fairy, for helping with the fix!
## [2.1.10] - 2016-02-14
### Fixed
- Fixed a potentially serious bug where updates to Chrome could break Epichrome apps permanently, so they'd have to be deleted and recreated. The internal ChromeEngine in each app had Info.plist keys that would cause it to try to auto-update and that would break it. Those keys are now removed.
View
@@ -711,8 +711,7 @@ function linkchrome { # $1 = destination app bundle Contents directory
# UTExportedTypeDeclarations ''
# SCMRevision ''
# NSHighResolutionCapable true
local filterkeys=(CFBundleExecutable string "$chromeEngineName" \
CFBundleIconFile string "$CFBundleIconFile" \
local filterkeys=(CFBundleIconFile string "$CFBundleIconFile" \
CFBundleTypeIconFile string "$CFBundleTypeIconFile" \
DTSDKBuild '' \
DTSDKName '' \
@@ -728,8 +727,11 @@ function linkchrome { # $1 = destination app bundle Contents directory
# filter Info.plist file from Chrome
filterchromeinfoplist "$1" "$tmpEngineContents" "${filterkeys[@]}"
# create link to Chrome executable in engine's MacOS directory
# create links to Chrome executable in engine's MacOS directory
try /bin/ln -s "$chromeExec" "$tmpEngine/$engineExec" "Unable to link to Chrome Engine executable"
try /bin/ln -s "$chromeExec" "$tmpEngineMacOS" "Unable to link to Chrome Engine dummy executable"
# create dummy executable in engine's MacOS directory
# recreate Resources directory (except for .lproj directories & icons)
local chromeResources="$chromeContents/Resources"
View
@@ -1,2 +1,2 @@
# Epichrome version
mcssbVersion=2.1.10
mcssbVersion=2.1.11

0 comments on commit fe32954

Please sign in to comment.