gautierdag
commented
4 years ago I was able to scrape your profile just fine on the latest version 1.0.20 and using cookies.
const fs = require("fs");
const scrapedin = require("scrapedin");
const puppeteer = require('puppeteer')
async function main() {
let browser;
try {
console.log("Scraping");
const linkedInUrl = "https://www.linkedin.com/in/emanfateen/";
const cookies = fs.readFileSync("cookies.json");
const puppeteerArgs = {}
const args = Object.assign({
headless: true,
args: ['--no-sandbox']
}, puppeteerArgs)
browser = await puppeteer.launch(args)
const wsEndpoint = await browser.wsEndpoint()
const options = {
cookies: JSON.parse(cookies.toString()),
hasToLog: true,
isHeadless: true,
endpoint: wsEndpoint
};
const profileScraper = await scrapedin(options);
const linkedInProfile = await profileScraper(linkedInUrl);
console.log(linkedInProfile);
} catch (err) {
console.log(err)
} finally {
if (browser) {
await browser.close()
}
}
}
main();Have you tried scraping a profile that is not your own ? Sometimes linkedin displays different pages for when you are viewing your own profile which can potentially break the scraper.
EmanFateen
raphaelpreston
Hello, I'm using scrapedin with version 1.0.20 and this line
const profile = await profileScraper('https://www.linkedin.com/in/emanfateen/')and here is my logI'm logging by cookie and here is my settings scraper: { hasToLog: true, isHeadless: true, puppeteerArgs: { args: [ '--no-sandbox' ] }, interval: 13000, }
how could I solve this issue!!