Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
0.2.5 still can't save new token format
See original GitHub issuepattern="[\da-f]{40}" is still present in 0.2.5
related #51
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
How to authenticate with keycloak through authorization code ...
I 'm trying to authenticate my flutter app to keycloak following the repo ... is an access token saved in the secure storage...
Read more >Setting Up a Personal Access Token via R - The Carpentries
There are a few possible errors you might see, but the remedy is always the same: get a new token and register it...
Read more >Retrieve an Access Token and Refresh Token
To request the user's access token from Login with Amazon, make a secure HTTP POST ... The refresh token that can be used...
Read more >Can't save Google Access Code | WordPress.org
1. Open a Private window and click to get code and get a new auth code and copy the code and click on...
Read more >What Are Refresh Tokens and How to Use Them Securely
This post will explore the concept of refresh tokens as defined by OAuth 2.0. We will learn how they compare to other token...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
0.2.6 has been submitted to the respective extension stores, let me know if you have any more problems after the new version goes live 😃
Ah, thanks for the screenshot! You are indeed seeing the ReEnterInvalidToken view, from which I had forgotten to remove the token validation.
I removed all token validation attempts and just let you enter whatever.
0.2.6 also contains some more quality of life fixes: