Git Product home page Git Product logo

Comments (4)

davidbuchanan avatar davidbuchanan commented on June 2, 2024 1

Yeah that worked! Thank you for your patience.

PR

from build-your-own-radar.

devansh-sharma-tw avatar devansh-sharma-tw commented on June 2, 2024

Hi @davidbuchanan , the Google Sheet tests in Cypress require the CLIENT_ID and API_KEY to be set, as trying to get data from a Google Sheet requires a manual Google login, which we cannot do with Cypress. The alternative is to set these variables which provide Cypress with an authenticated session for a public sheet (details here).

Could you confirm if you have these variables exported in the session you are running the tests ? If you do, could you please check if the Authorized JavaScript origins is set with http://localhost:8080 in GCP console ?

FYI - docs state request a trailing '/', this also did not work for me.)

Yeah, the / is not required, I'll update the README for it.

Thanks!

from build-your-own-radar.

davidbuchanan avatar davidbuchanan commented on June 2, 2024

I confirm I did NOT! My bad RTFM totally on me.

I have tried to do as suggested but now hit an issue with GCP.

  1. Google Developer Console
  2. CLICK: 'Configure a project'
  3. SELECT: [my-test-project]
  4. SELECT: 'Web Browser' from 'Configure your OAuth Client'
  5. INPUT for 'Authorized Javascript Origin': 'http://localhost:8080'
  6. CLICK 'CREATE'
    Form renders validation error 'schema must be https'.
    This is in conflict with the google direction on the previous page which states
    'When you configure the project, select the Web browser client type and specify the origin URI of your app. When you perform tests, both http://localhost and http://localhost:<port_number> must be added to the Authorized JavaScript origins field.'

That said the form field description states https.

Again apologies if I am being dumb here.
google-api-for-sheets_https-only

from build-your-own-radar.

devansh-sharma-tw avatar devansh-sharma-tw commented on June 2, 2024

Hi, no worries! I think what you might have landed on is very specific to Google Sign In related IDs.

Could you try creating a project directly on GCP console and create keys there ?
Once on the console, you should be able to create the Client ID and API Key from APIs & Services section.

Thanks!

from build-your-own-radar.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.