Closed muschellij2 closed 2 years ago
Perhaps the token you are testing with was created under different scopes? Nevertheless I would hope this is fixed/issue resolved via gargle
to avoid special logic here.
This looks like its solved in dev release of gargle
https://github.com/r-lib/gargle/issues/187
Added a temporary fix for https://github.com/r-lib/gargle/issues/187. If you pass in a Token2.0 into
gar_auth
with the newer version of gargle it uses bring your own (byo) token. I don't know what you're testing on and since it's got differential behavior in non-interactive auth, I'm not sure how you'd test. I think this could potentially be a large breaking change if people's workflows implicitly relied on thegargle
behavior, so I'm not sure if you want to incorporate or just wait forgargle
to determine if they are going to handle this edge case.