about 3 minutes after I refresh the token by validating it on a version-test page, the error pops back up in the API connector
what’s happening on the user side:
2 scenarios here.
1 is if the user is already logged into their LinkedIn account when they sign up using LinkedIn on my website; and the 2nd scenario is when the user is not currently logged into LinkedIn when they sign up on my website using the LinkedIn. Both of these scenarios are occurring while an error exists in the Bubble API Connect Plugin “Your token is not valid any more. You should sign up again in run mode to get a token to set up and modify your calls”
After the user clicks on the “log in with LinkedIn” button they’re navigated to LinkedIn oath page asking them to log in. After they enter their credentials and login, they’re NOT asked if they want to share data with my website, they’re simply redirected immediately back to my website as a logged in user with their name and email address associated with they’re account.
After the user clicks on the “log in with LinkedIn” button they’re navigated to LinkedIn’s oath page asking them share data with my website, once approving, they’re navigated back to my website as a logged in user with their name and email address associated with they’re account.