chore: remove access token thats unnecessary (GA4) #159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
pnadolny13
changed the title
pnadolny13
added a commit
that referenced
this pull request
Mar 12, 2024
This makes the same changes as #159 but on the UA branch. --------- Co-authored-by: Edgar Ramírez Mondragón <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The method that was previously used to manage OAuth tokens had issues with refreshing (see #155) and it expected an access token to be provided which is unnecessary.
I was able to sync data from a test account using these changes. I think the CI job only uses client_secrets.json.