Peter Andrews
Peter Andrews
FF 43.0 looks fine. I'm only seeing the problem in 44.0. It's either an FF bug or a problem with our nsIProtocolHandler implementation. https://github.com/petea/sage/blob/master/src/components/sageProtocolHandler.js https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIProtocolHandler
I'm not seeing this on OS X or Windows. Can you provide steps to reproduce here?
Related Get Satisfaction topic: https://getsatisfaction.com/sagerss/topics/ever-since-installing-firefox-48-0-the-sage-protocol-ceases-to-work
The URL looks right. Can you tell me what OS you're on?
Could you try creating a clean test profile, install Sage, and see if you get the same results? https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
_From [email protected] on April 06, 2011 16:02:03_ Related Get Satisfaction topic: http://getsatisfaction.com/sagerss/topics/no_flash_into_feeds
> @petea can this issue be closed? Yes, this was addressed in 1.3.1.
Can you provide more detail about your use case? What's the scenario in which you only have an `OIDTokenResponse` with which to instantiate `OIDAuthState`? Typically, there would be an associated...
This is a CocoaPods issue related to watchOS simulator selection. CocoaPods/CocoaPods#11558
Can you tell me what errors you're seeing and how you generate them?