Issue on MacOS - Not logged in error in log.txt #33
-
Unable to scrap the content. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 7 replies
-
@iamrsoze I need more details, and a screenshot of the terminal where the error occurred. |
Beta Was this translation helpful? Give feedback.
-
It was the incorrect version of Chrome browser that was causing the issue. Works smoothly on Chrome 98. Any leads on how can I stop that? |
Beta Was this translation helpful? Give feedback.
-
The binary from the github repo isn't working for me (attached screenshot). |
Beta Was this translation helpful? Give feedback.
-
@iamrsoze any updates? |
Beta Was this translation helpful? Give feedback.
-
I know what you're saying to do a "Allow Anyway" in Settings -> Privacy & Security. PS - I don't have any other chrome installed on Mac. I am just copying this in Chrome-bin folder and trying to open via command line. |
Beta Was this translation helpful? Give feedback.
-
@iamrsoze Step 1: Double click on Chromium app to open, If it shows damaged then check for Security and Privacy -> General Settings to allow access to chromium. |
Beta Was this translation helpful? Give feedback.
-
@iamrsoze new update was released few days ago, reclone to a new location and test it in your system |
Beta Was this translation helpful? Give feedback.
@iamrsoze
Follow this tutorial
https://user-images.githubusercontent.com/48487849/222886869-4f815acf-cde0-4aff-b978-9c66c598ef9c.mp4
Step 1: Double click on Chromium app to open, If it shows damaged then check for Security and Privacy -> General Settings to allow access to chromium.
Step 2: If it still shows then open a terminal inside mac folder and run the following command : xattr -cr Chromium.app
Now it should fix the issue and chromium should open up if it doesn't recheck step 1.