Closed o-fernandez closed 7 years ago
Yep, it's a known issue. I just pushed a fix in v0.92 to the Chrome Web Store. It's currently pending review but will hopefully be live soon.
On Fri, Mar 31, 2017 at 3:16 PM, omar fernandez notifications@github.com wrote:
I use the https everywhere extension (https://www.eff.org/https-everywhere) and sometimes I get an error message on SmileAlways saying that there's a conflict between the two apps. It seems that the two apps try to modify the URL, one to take me to https:// and the other to smile.amazon.com, but somehow they clash. Is there a way to ensure that this doesn't happen?
[image: screen shot 2017-03-31 at 3 14 23 pm] https://cloud.githubusercontent.com/assets/13389997/24571255/caad1b1c-1624-11e7-99a3-c5d314152116.png
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Jdhaimson/smilealways/issues/38, or mute the thread https://github.com/notifications/unsubscribe-auth/AEMLEK6OAtmQL926mbpwoZGodry2rsu1ks5rrXtKgaJpZM4MwNuq .
I use the https everywhere extension (https://www.eff.org/https-everywhere) and sometimes I get an error message on SmileAlways saying that there's a conflict between the two apps. It seems that the two apps try to modify the URL, one to take me to https:// and the other to smile.amazon.com, but somehow they clash. Is there a way to ensure that this doesn't happen?