Cannot capture webpage

[sopoforic]

2.0 beta 31 on chrome 84

Attempting to save this page with the chrome extension fails. It appears to work, but the page it redirects to (like this one) gives an error, Ouch. No document found for this ID..

I have attempted to save this page several times without success.

[sopoforic]

Actually, it looks like I cannot save any pages at all, this morning.

[burtonator]

@sopoforic was this ever resolve for you? I'm wondering if it's connected to your bug with the desktop app.

[sopoforic]

It is working again now, yes.

[juaoose]

I also seem to have a strange behaviour with the extension... On some pages when I click the extension button and then click "Save to Polar" nothing happens.

From the browser console:

Starting capture...
DevTools failed to load SourceMap: Could not load content for chrome-extension://jkfdkjomocoaljglgddnmhcbolldcafd/content-bundle.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
content-bundle.js:2 Captured:  {description: "AWS recommends using just a single DynamoDB table …ou would do that and the few times you shouldn't.", icon: "https://www.alexdebrie.com/posts/dynamodb-single-table/favicon.ico", image: "https://user-images.githubusercontent.com/6509926/53833786-0166ee80-3f4f-11e9-8edf-0fd168b04c82.png", keywords: undefined, title: "The What, Why, and When of Single-Table Design with DynamoDB", …}content: "<div><div><p>I’ve become a big proponent of Dynamo"description: "AWS recommends using just a single DynamoDB table for your entire application. In this post, learn why you would do that and the few times you shouldn't."excerpt: "AWS recommends using just a single DynamoDB table for your entire application. In this post, learn why you would do that and the few times you shouldn't."icon: "https://www.alexdebrie.com/posts/dynamodb-single-table/favicon.ico"image: "https://user-images.githubusercontent.com/6509926/53833786-0166ee80-3f4f-11e9-8edf-0fd168b04c82.png"keywords: undefinedlanguage: undefinedprovider: "alexdebrie"text: "I’ve become a big proponent of DynamoDB over the p"title: "The What, Why, and When of Single-Table Design with DynamoDB"type: "article"url: "https://alexdebrie.com/posts/dynamodb-single-table/"__proto__: Object
content-bundle.js:2 Content script loaded

[sopoforic]

And today I am getting this issue again in 2.0.56 in chrome 84.

[sopoforic]

I have had this issue intermittently since initially reporting it. There doesn't seem to be any pattern--maybe it happens more commonly in the morning? It starts working again after a while, each time.

[sopoforic]

Webpage capture has been failing for me for the past few days.

[sopoforic]

I'm not sure what's failing. I have log entries like:

Starting capture...
DevTools failed to load SourceMap: Could not load content for chrome-extension://mklidoahhflhlpcpigokeckcipaibopd/content-bundle.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
content-bundle.js:2 Captured:  {description: undefined, icon: "https://en.wikipedia.org/static/apple-touch/wikipedia.png", image: "https://upload.wikimedia.org/wikipedia/commons/f/f6/OTVbelweder-front.jpg", keywords: undefined, title: "Parasocial interaction - Wikipedia", …}
content-bundle.js:2 Content script loaded
content-bundle.js:2 progress: type: determinate value: 0 {ref: {…}, id: "firebase-upload-6", task: 6, completed: 0, total: 34656, …}
content-bundle.js:2 progress: type: determinate value: 100 {ref: {…}, id: "firebase-upload-6", task: 6, completed: 34656, total: 34656, …}
Navigated to https://app.getpolarized.io/doc/12nFwCUvJb

I see a 404 in the extension logs for the URL that should contain the new doc, but if I navigate there myself, the doc seems to exist.

This seems to indicate that the document is getting uploaded correctly, but isn't yet available when the extension tries to send the browser there. Or something. In any case, this document never shows up in the library, even though it exists on the server.

[sopoforic]

Coincidentally, I have discovered what seems to be happening in this case. I had created a second account to use in testing the 2.0 beta, and stopped using it once 2.0 was stable. Upon logging into that account again, after a gap of a couple of months, I found that the documents which had failed to capture had in fact appeared in the secondary account.

So, the browser extension is intermittently using the wrong credentials when capturing pages. I haven't been using the secondary account, so I have no idea what would prompt the extension to make this mistake.