-
Notifications
You must be signed in to change notification settings - Fork 5
Obscure error when running gc_auth #20
Comments
gc_auth(new_user = TRUE, cache =TRUE ), if you pull the help log you will see that this is a third set-able option in the .Rprofile as well. |
Thanks @Karnner2 for resolving the error. The @benjcunningham Does the Your help is appreciated. Thanks! |
@LiNk-NY , I know you asked @benjcunningham but the following works for me.
With respect to where the key generation occurs, yes, those should work. It appears that the code is just dated (possibly) and the Oath2.0 terminology has replaced the prior terminology that @benjcunningham used. It still works. You only need the client ID if you are going to be editing someone else's calendar through the API, but if I recall you need your app approved by Google in order to do this. The |
No, thanks for helping Jonathan! @Karnner2 For some reason, calling I used the
After authenticating successfully(?), I ran
It seems like there is a recursive call somewhere. I haven't looked into it. |
@LiNk-NY, you can ignore the errors for now. Although they are depreciated it should not actually matter for the time being. Be-careful with what you are getting though, the function
Also yes, there is no actual need to set up a After you have identified the calendar you want to manipulate using
the So you can pass headers ( |
@Karnner2 Thanks for all the help! I am able to see my events now. Cool example! It almost looks like a breakfast recipe for shakshuka 😉 All the best, |
I have a problem with auth as well, although it seems different. Whenever I would like to connect to the calendar through the package and the API, it fails. So after this I run I've tried many formats for gc_ls, also tried with different Google application (OAuth clients), and always get the same result. Does anyone have a suggestion for this? Thanks, |
Hi Berta! @BertaBojte It seems like you were able to authenticate okay. You then have to do something like: res <- gc_ls(pattern = "")
res$summary Best, |
I'm on the same page as Berta. res$summary ` |
Hi @abjeroen Make sure the authentication is complete after you get the browser pop-up. Best, |
@abjeroen |
I am with the same Errror as @BertaBojte I try to use gc_ls(pattern = "") and give me the Error: How can I fix this? Thanks |
Try gc_ls(pattern=“*”) or, if google’s backend is using regex you may need
to go that route, gc_ls(“.*”)
Right now you are asking it to find “string null” and that might be the bad
request.
…On Thu, Dec 29, 2022 at 4:23 AM oscarepaezm ***@***.***> wrote:
I am with the same Errror as @BertaBojte <https://github.com/BertaBojte>
After "Authentication complete."
I try to use gc_ls(pattern = "") and give me the Error: Error in
httr::GET(url, gc_token()) %>% httr::stop_for_status() : Bad Request (HTTP
400).
How can I fix this?
Thanks
Oscar
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALHTXJHBMQQMIS2NUC4TVF3WPVJ77ANCNFSM4KRUW3BQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I also see Marcel has forked the correction. While I haven’t examined
either the original main branch source or Marcel’s fork, based on the
description—the gc_ls uses build_url and that build_url at one point
required the API key to be in it for the API’s server to accept the
request.
Google may have updated their end-point and so you will need to update as
well. So try using Marcel’s fork and or what I referred to and see if that
doesn’t fix your problem. Let us know if not.
On Thu, Dec 29, 2022 at 9:26 AM Jonathan Fluharty ***@***.***>
wrote:
… Try gc_ls(pattern=“*”) or, if google’s backend is using regex you may
need to go that route, gc_ls(“.*”)
Right now you are asking it to find “string null” and that might be the
bad request.
On Thu, Dec 29, 2022 at 4:23 AM oscarepaezm ***@***.***>
wrote:
> I am with the same Errror as @BertaBojte <https://github.com/BertaBojte>
> After "Authentication complete."
>
> I try to use gc_ls(pattern = "") and give me the Error: Error in
> httr::GET(url, gc_token()) %>% httr::stop_for_status() : Bad Request (HTTP
> 400).
>
> How can I fix this?
>
> Thanks
> Oscar
>
> —
> Reply to this email directly, view it on GitHub
> <#20 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ALHTXJHBMQQMIS2NUC4TVF3WPVJ77ANCNFSM4KRUW3BQ>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Now with Thanks so much! |
@benjcunningham
I am not sure if I'm providing the right credentials and the instructions are not very clear.
I am getting an error when I added my
googlecalendar.client_key
andgooglecalendar.client_secret
in my~/.Rprofile
file.I must be missing something... Did you mean
client_id
andclient_secret
as shown here?https://weblizar.com/blog/get-google-calendar-client-id-and-client-secret-key/
If so, I've tried that and it doesn't work. I've also tried using my
API Key 1
as thegooglecalendar.client_key
value and the client secret but to no success.It would be good to have a template / description of what these keys look like or a step-by-step on how to obtain them as above.
Thanks,
Marcel
Created on 2020-02-07 by the reprex package (v0.3.0)
The text was updated successfully, but these errors were encountered: