Google People API Error
-
I'm refactoring some code that imports Google contacts. This screenshot[^] shows the parameters being sent. It is identical to the previous version, with the exception of the Client Id and Client Secret. Now, for some reason, I'm getting this:
Google.Apis.Requests.RequestError
Request had insufficient authentication scopes. [403]
Errors [
Message[Insufficient Permission] Location[ - ] Reason[insufficientPermissions] Domain[global]
]This appears to be complaining about the scope, yet it's hasn't changed. Not sure if that's what this message means. I've been Googling & reading the docs, and I don't see what's wrong. I'm really stuck on this. Can someone point me in the right direction?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
I'm refactoring some code that imports Google contacts. This screenshot[^] shows the parameters being sent. It is identical to the previous version, with the exception of the Client Id and Client Secret. Now, for some reason, I'm getting this:
Google.Apis.Requests.RequestError
Request had insufficient authentication scopes. [403]
Errors [
Message[Insufficient Permission] Location[ - ] Reason[insufficientPermissions] Domain[global]
]This appears to be complaining about the scope, yet it's hasn't changed. Not sure if that's what this message means. I've been Googling & reading the docs, and I don't see what's wrong. I'm really stuck on this. Can someone point me in the right direction?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
If you are refactoring code, and it worked before you started, then the obvious thing to do is go back to the original code and compare it to the refactored version - it's quite likely that scope for a variable has changed and it was (or is) "hiding" the required value, or perhaps you a missing a call that you needed before. But without the original and refactored code, there really isn't anything we can do!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
If you are refactoring code, and it worked before you started, then the obvious thing to do is go back to the original code and compare it to the refactored version - it's quite likely that scope for a variable has changed and it was (or is) "hiding" the required value, or perhaps you a missing a call that you needed before. But without the original and refactored code, there really isn't anything we can do!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
The code is different because Google changed their auth process.
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
The code is different because Google changed their auth process.
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
That's not refactoring! Refactoring is the process of restructuring code, while not changing its original functionality. The goal of refactoring is to improve internal code by making many small changes without altering the code's external behavior. You need to find out what the new process involves, and upgrade the code to be compliant. At a guess, Google will have a list of changes that need to be made - I'd start there, or ask their tech support.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
