[Bug] I cannot authenticate

[lindamacdonald]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• Platform: [Figma / Sketch / XD]
• OS: [Mac / Windows]
• Browser [e.g. chrome, safari]
• Version [e.g. 202x.0.x.x]

Additional context
Add any other context about the problem here.

[softmarshmallow]

Hi. Thanks for the report. Can you share us the log from the console or capture the screen so we can take a deeper look?

[lindamacdonald]

hey there :)
yes I reviewed the console error and its:

it comes from the allow access page and the button on the page is inactive

[lindamacdonald]

I have tried on chrome, firefox and edge and the issue is accross all of them

[lindamacdonald]

there are also some cookie setting issues
Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform
A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. Starting in Chrome 101, the amount of information available in the User Agent string will be reduced.
To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.
Note that for performance reasons, only the first access to one of the properties is shown.
1 source
options_prefs.js:1
Learn more: User-Agent String Reduction
Indicate whether a cookie is intended to be set in a cross-site context by specifying its SameSite attribute
Because a cookie’s SameSite attribute was not set or is invalid, it defaults to SameSite=Lax, which prevents the cookie from being set in a cross-site context. This behavior protects user data from accidentally leaking to third parties and cross-site request forgery.
Resolve this issue by updating the attributes of the cookie:
Specify SameSite=None and Secure if the cookie is intended to be set in cross-site contexts. Note that only cookies sent over HTTPS may use the Secure attribute.
Specify SameSite=Strict or SameSite=Lax if the cookie should not be set by cross-site requests.
5 cookies
Name Domain & Path
csrf-state-legacy figma-production-admin.auth.us-west-2.amazoncognito.com/
sid figma.okta.com/
autolaunch_triggered figma.okta.com/
JSESSIONID figma.okta.com/
t figma.okta.com/
Learn more: SameSite cookies explained

[softmarshmallow]

Thank you. that log seems to be irrelevant to our plugin.
As far as I can tell, you may wait for about 30 seconds after you complete authentication on the browser until the plugin reacts with the response.

1

2

After about 3 ~ 10 seconds