I have installed the module and google secret. I have followed the steps recommended in the wizard but in the last step it told me that:
"google calendar could not be used with the supplied credentials: file "" does not exist"

I have uploaded the service key json file both as managed file and uploading to server and entering the full path, same result. When check the settings page I see that the key is readable and content is there, but after the error above, no calendar is found.

When I was creating service key, Google notified me not to use that method and suggested another one, maybe the structure is changing? Does anyone encountered this? Any suggestions?

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

loker created an issue. See original summary.

loker’s picture

I have managed to make it work while trying manually entering the information somehow. The wizard didn't work but at the end calendar works. So it seems it was my bad I guess.

rivimey’s picture

Status: Active » Closed (outdated)

@loker, I'm sorry there was a problem, glad you got there in the end.

raulmangolin made their first commit to this issue’s fork.

raulmangolin’s picture

StatusFileSize
new849 bytes

It was just a validation issue. Fixed it with this patch attached.

edmargomes’s picture

Status: Closed (outdated) » Needs work

The patch #5 works, but need change to get with one option, or config->storage->get or config->get

mortona2k made their first commit to this issue’s fork.

  • rivimey committed 4cda2af4 on 3.0.x authored by raulmangolin
    Issue #3283062 by raulmangolin: google calendar could not be used with...
rivimey’s picture

Thanks for identifying the fix.

@edmargomes I don't really understand comment 7, can you elaborate?

rivimey’s picture

Version: 8.x-2.3 » 3.0.x-dev
rivimey’s picture

Category: Support request » Bug report
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.