You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello there, in Apify CLI, when I do apify login and select Through Apify Console, it takes me to the web where I click Log in, but then I get this error: Error: Could not send API token to CLI
It might not necessarily be a bug on the product side but since there's literally no information on how to fix that - directly there or anywhere on Apify's websites, I'd consider it a bug as a customer.
Btw. if I close the modal confirmation, it also claims an error. This time: Error: Could not send exit command to Apify CLI
Followup:
Hi! I have the same issue. The token is created, but got the error message. The solution is to cancel the process and select to use the token manually, then it works with the token created in the previous step ...
The text was updated successfully, but these errors were encountered:
Jkuzz
added
the
t-tooling
Issues with this label are in the ownership of the tooling team.
label
Aug 9, 2024
After some investigation, it seems that the issue is a mix of browser filtering and console (Brave seems to block it with their integrated adblocker for some reason)
Reported in slack. Original message below:
Hello there, in Apify CLI, when I do apify login and select Through Apify Console, it takes me to the web where I click Log in, but then I get this error:
Error: Could not send API token to CLI
It might not necessarily be a bug on the product side but since there's literally no information on how to fix that - directly there or anywhere on Apify's websites, I'd consider it a bug as a customer.
Btw. if I close the modal confirmation, it also claims an error. This time:
Error: Could not send exit command to Apify CLI
Followup:
Hi! I have the same issue. The token is created, but got the error message. The solution is to cancel the process and select to use the token manually, then it works with the token created in the previous step ...
The text was updated successfully, but these errors were encountered: