I should add that some of the processing is occurring correctly. If I use an account with two step authentication I get requests for verification code and option of alternative methods. So the OAUTH 2 transaction error may be occurring after authentication. Some javascript call is failing?
On Saturday, June 6, 2015 at 8:16:15 AM UTC-5, [email protected] wrote: > > MarsEdit is a well regarded OS X blog authoring app. It used to support > Blogger but the sole dev missed deprecation of ClientLogin. He's now > switched to OAUTH. > > > His implementation works for most people, and it works on my machines > (Mavericks and Yosemite). Works, that is, except for my primary user > account (Mavericks) where, on authentication attempt against the embedded > Google authentication app, I get: > > > You've reached this page because we have detected that Javascript is >> disabled in your browser. The page you attempted to load cannot display >> properly if scripts are disabled. >> Please enable scripts and retry the operation or go back in your browser. > > > Based on Inspector use the error message is coming from a noscript file > returned by accounts.google.com. Return is very quick (cached)? > > I think the error message is misleading. Javascript is enabled in my OS X > browsers - Safari and Chrome. I presume this dialog is using WebKit though, > and I can't speak to the state of WebKit. > > I am able to to authenticate with similar dialogs for Google Photos > Backup, Google Drive, and so on. > > So something is wrong, but it's hard to debug. It's something in my > Mavericks environment, perhaps something to do with WebKit. > > Anyone have any ideas on anything to try? > > Thanks! > -- You received this message because you are subscribed to the Google Groups "OAuth" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
