warpdotdev
Can't get into Warp Terminal -- neither after login, nor from other url
Discord username (optional)
No response
Describe the bug
I logged in using Google but got no farther. The Take Me to Warp button had no effect. It was very slow but I was able eventually click on the other url. It brought up a web page but it did nothing either. My web browser is chrome on Windows. My Linux environment is Ubuntu on WSL.
To reproduce
See above
Expected behavior
A usable terminal.
Screenshots
No response
Operating system
Linux
Operating system and version
Ubuntu 22.04.4 LTS on WLS / Windows 11
Shell Version
bash 5.1.16
Current Warp version
warp-terminal_0.2024.04.16.08.02.stable.00_amd64.deb
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
never
Additional context
Btw, you probably lose a lot of potential warp logs by not making that command copiable. Probably only old coders like me would bother to meticulously type it in.
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
Hi @phdye thanks for your patience. Sorry to hear about the login issues. We've added a list of workarounds here: https://docs.warp.dev/help/troubleshooting-login-issues
The main thing you need is to copy the authentication token (what you may be referring to as the "other url") from the Login page. On Warp for Linux, the default copy-and-paste Keyboard shortcuts are CTRL-SHIFT-C and CTRL-SHIFT-V respectively. You may also need to change your default $BROWSER to chrome or firefox on WSL to workaround the "take me to warp" login issue.
Also, make sure to download the latest version as we release fixes every week. https://docs.warp.dev/getting-started/changelog
Hope this helps, let me know if the issue persists.
I'm blocked logging in on Ubuntu as well. I can't access https://app.warp.dev/logged_in/remote?is_user_new=false&scheme=warp. It's rendered correctly once then is replaced with "An error has occurred" (though it's impossible to read because it's a black font on black background), here's the entire contents of the console when I try to load that page in Firefox with all extensions disabled:
Cookie warnings 7
Cookie “__tld__” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite [index.ts:96:2](https://app.warp.dev/analytics-js-cookies/src/component-cookie/index.ts)
Cookie “__tld__” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite [index.ts:96:2](https://app.warp.dev/analytics-js-cookies/src/component-cookie/index.ts)
The value of the attribute “expires” for the cookie “_ga_5NBFZJQ82M” has been overwritten. [js:398:271](https://www.googletagmanager.com/gtag/js?id=G-5NBFZJQ82M)
Cookie “_ga_5NBFZJQ82M” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 [js:398:271](https://www.googletagmanager.com/gtag/js?id=G-5NBFZJQ82M)
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite [js:398:271](https://www.googletagmanager.com/gtag/js?id=G-5NBFZJQ82M)
The value of the attribute “expires” for the cookie “_ga_5NBFZJQ82M” has been overwritten. [js:398:271](https://www.googletagmanager.com/gtag/js?id=G-5NBFZJQ82M)
Cookie “_ga_5NBFZJQ82M” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 [js:398:271](https://www.googletagmanager.com/gtag/js?id=G-5NBFZJQ82M)
Error: Minified React error #301; visit https://reactjs.org/docs/error-decoder.html?invariant=301 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
React 11
setResult useQuery.ts:556
e useQuery.ts:260
yd module.js:137
gd module.js:176
error module.js:229
d iteration.ts:13
$d iteration.ts:13
reportError ObservableQuery.ts:1043
error ObservableQuery.ts:944
d iteration.ts:13
$d iteration.ts:13
error Concast.ts:183
yd module.js:137
gd module.js:176
error module.js:229
i asyncMap.ts:36
Caused by: React ErrorBoundary Error: Minified React error #301; visit https://reactjs.org/docs/error-decoder.html?invariant=301 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
i_ ApolloWrapper.tsx:117
n Route.js:30
n Switch.js:12
DT app.tsx:49
n Router.js:16
n BrowserRouter.js:10
i errorboundary.tsx:104
[console.ts:40:19](https://app.warp.dev/static/node_modules/@sentry/src/instrument/console.ts)
Bn console.ts:40
React 13
setResult useQuery.ts:556
e useQuery.ts:260
yd module.js:137
gd module.js:176
error module.js:229
d iteration.ts:13
$d iteration.ts:13
reportError ObservableQuery.ts:1043
error ObservableQuery.ts:944
d iteration.ts:13
$d iteration.ts:13
error Concast.ts:183
yd module.js:137
gd module.js:176
error module.js:229
i asyncMap.ts:36
Download the Apollo DevTools for a better development experience: https://addons.mozilla.org/en-US/firefox/addon/apollo-developer-tools/
Okay so After some Testing, it seems that using chrome instead of Firefox showed me the Auth code which i was able to Paste into Warp.
@phdye are you still seeing the same issue? Do you have access to ping app.warp.dev?