-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: LinkedIn Projects Query Selector is not inputing data #221
Comments
@a0m0rajab Maybe you can provide more context on why this does not work anymore? I tried increasing the timeout milliseconds but that didn't help either. |
I could not reproduce it on: https://github.com/open-sauced/ai/releases/tag/v1.12.0-beta.1 |
July.18.2023.20_05.PGrElRTYB6kE-XbzReNVugAcvREehfpkbqdTyesQ5ZrkGejWY.mp4 |
Can we get on a call to debug this? It seems to work only for you, maybe you can tell what's wrong once you see what's happening on my end? |
Sure! I will message you on discord. |
we did a check with @diivi and could not find a full answer for that, he will write the update about our call. |
Had a one-hour call with @a0m0rajab today regarding this, thank you for your patience! It seems to be working fine on his PC, but I'm facing some issues. We found a workaround by not changing the active tab to the LinkedIn page. This method fills the data nicely, albeit in the background. We'll conduct some more testing, and if it doesn't work uniformly for both of us, we'll revert to the |
Did this work before, by the way? or was it only working on my side the whole time? I tried to test this again by:
If it worked before, can someone just try to fresh install the repo on new folder and try it? and in both cases worked for me, I am not sure how to test it right now, if anyone from @open-sauced/triage has a time to check, I would love to do pair programming session with you. If not you can check the next to debug it and share your insights with us: What I am thinking to test is the next:
To test this we need to do the next: In the lines of the fetching: Lines 184 to 197 in 311f456
We need to remove the script running lines and print the data on console.log if we get data from the fetch then it's okay. This will be need to checked in the popup DevTools.
to do this we can simply change the callback function in our script, to do this do the next: Lines 170 to 183 in 311f456
Check if this has been printed in the linkedIn DevTools. If it worked, then we have a functioning scripts.
Try to change the active tab to false and check if the script is running. Line 186 in 311f456
For further understanding of the code that's written you can check: |
talked with @takanome-dev he got the same issue, it did not work. Thank you for your time! |
I didn't try it using the dev build though, will give it a shot 👍 Update: Tried the steps mentioned above but still nothing. One thing I noticed is after setting the active tab to false and clicking cc @a0m0rajab @diivi |
Might be the case that your linked is different. Are you paying for any features or opted into anything? It might be worth trying a different LinkedIn account entirely. |
@takanome-dev I do not think that the tab is the issue, the logic of the code is being like the next:
since the tab is being opened we know that the code fetched something from GitHub, what I am not sure about is the next:
I have a normal account, no beta neither paid features! I will try a friend account though. |
I got the response from github but couldn't see the data in
Which selectors? (not very familiar with the codebase 😅) |
@takanome-dev selector in linkedin page, to test this we can do the next:
const inputFields = document.querySelectorAll(".artdeco-text-input--input");
inputFields[0].value = "Test";
inputFields[1].value = "Test Desc"; if it works then the linkedin selectors does not change and the issue is in the callback function. As for me I have tried this with another PC, it was a Chromebook, it did not work on my profile or my friend's profile. Would the operating system differ or the chrome API? |
Alright, what's happening is that Github returns It works by removing that trailing slash and setting the active tab to false (not sure why) 😄 const getRepoAPIURL = (url: string) => url.replace(/github\.com/, "api.github.com/repos").replace(/\/$/, ""); |
When I add the trailing slash, the extension adds undefined text to the text we fill with, here is the video: www_screencapture_com_2023-7-28_17_54.mp4 |
My chrome version is: Version 114.0.5735.248 (Official Build) (64-bit) |
I opened a PR to just add a function to have logs being unified with us, if the log is not printed in the linkedin page console, then the excute script is not working... |
Yeah, because Github returns a not found
I don't think so. Mine is Version 115.0.5790.102 (Official Build) (64-bit)
Tried it but no way I could see it 😂 |
What I meant here is that the extension works even if GitHub returns not found.
So nothing is printed on the console? |
😄 That's a move forward! was the active tab option false or true? and what is the timeout number that you used? |
false
5000 ms. Maybe that's too much but it gave me the time to switch to the opened LinkedIn tab and open the console |
Did it work when the active tab were true? |
No, it didn't work |
🎉 This issue has been resolved in version 1.14.1-beta.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 1.14.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Describe the bug
When submitting a project to LinkedIn, I have not been able to get the title and body to to be filled.
Steps to reproduce
Browsers
Chrome
Additional context (Is this in dev or production?)
I am not sure if the selector is working.
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: