linkeddata
Error: Unable to save: failed to fetch
After signing in with my WebID from solid.community, I tried to "Save As" a web page but got an error: Unable to save: failed to fetch.
My dokieli version is 03.21 and the web browser is chrome.
I also cleared old credentials from my browser and repeated the steps but the error still persists.
What should I do?
@emekaokoye, thanks for reporting! I presume you're using the dokieli extension (from Chrome store) and not just a webpage with existing dokieli embedded.
When you say you sign in with your WebID, did you mean that you entered the URI in the Sign in dialog or did you go through the OpenID Connection authentication process (and selected your identity provider)?
Besides the authentication issue, you probably already have a folder with name public and one possible issue with what you're attempting to do is that, it is trying to create a file with the same name. AFAIK, that will not succeed that way. We can come back to this point.. so, for the time being just test with something like https://.... /public/foo
@kidehen, you mentioned that you had to logout/in again to make it work. Can you elaborate? I haven't experienced this issue. Is the session being cleared somehow between states? When is the exact moment that it is gone?
I certainly would like to replicate the issue.
@csarven , Scenario to leads to the save failure on my end:
- Interact with some doc via dokie.li extension
- Go about my normal business
- Stumble across a new doc of interest
- Click on dokie.li extension icon
- Attempt "Save As"
- Failure happens here
- Logout
- Login
- Repeat "Save As" attempt
- Works
Note this happens from: Google Chrome is up to date Version 71.0.3578.30 (Official Build) beta (64-bit)
/cc @smalinin @emekaokoye
@csarven https://github.com/csarven Thanks for your response.
- I used the dokieli extension (from Chrome store)
- I entered the URI in the Sign in dialog
- I already have a folder with name public
I will now try with "https://.... /public/foo" option and revert asap.
On Thu, Nov 8, 2018 at 12:03 PM Sarven Capadisli [email protected] wrote:
@emekaokoye https://github.com/emekaokoye, thanks for reporting! I presume you're using the dokieli extension (from Chrome store) and not just a webpage with existing dokieli embedded.
When you say you sign in with your WebID, did you mean that you entered the URI in the Sign in dialog or did you go through the OpenID Connection authentication process (and selected your identity provider)?
Besides the authentication issue, you probably already have a folder with name public and one possible issue with what you're attempting to do is that, it is trying to create a file with the same name. AFAIK, that will not succeed that way. We can come back to this point.. so, for the time being just test with something like https://.... /public/foo
@kidehen https://github.com/kidehen, you mentioned that you had to logout/in again to make it work. Can you elaborate? I haven't experienced this issue. Is the session being cleared somehow between states? When is the exact moment that it is gone?
I certainly would like to replicate the issue.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/linkeddata/dokieli/issues/257#issuecomment-436956963, or mute the thread https://github.com/notifications/unsubscribe-auth/AAePcDuY4Rri0bWvQbIX8eWjbBGXprLNks5utA-TgaJpZM4YT91D .
-- Regards,
Emeka Okoye. Mobile: +2348023139936 (NG), +233269310862 (GH) Skype: Emx2004 Twitter: http://twitter.com/emekaokoye Linkedin: http://ng.linkedin.com/in/emekaokoye *Blog: *http://linkedopendatang.blogspot.com/ http://ng.linkedin.com/in/emekaokoye Google+: https://plus.google.com/+EmekaOkoye/about https://plus.google.com/114457961627178656743/about About Me: http://about.me/emekaokoye
@csarven
The error still persists. I created a folder "foo" and i tried to "save as" into https://emekaokoye.solid.community/public/foo/ .
Debug output: 2018-11-08T23:57:37.115Z: DO.C.User removed. branch-latest.min.js:58 XHR finished loading: GET " https://api.branch.io/v1/has-app/key_live_ofxXr2qTrrU9NqURK8ZwEhknBxiI6KBm?browser_fingerprint_id=546886649384592503&instrumentation=%7B%22%2Fv1%2Fhas-app-brtt%22%3A%221072%22%2C%22%2F_r-brtt%22%3A%221080%22%7D ". Hb @ branch-latest.min.js:58 h @ branch-latest.min.js:59 Ib @ branch-latest.min.js:60 Z.b @ branch-latest.min.js:120 h @ branch-latest.min.js:123 (anonymous) @ branch-latest.min.js:121 branch-latest.min.js:58 XHR finished loading: GET " https://api.branch.io/v1/has-app/key_live_ofxXr2qTrrU9NqURK8ZwEhknBxiI6KBm?browser_fingerprint_id=546886649384592503&instrumentation=%7B%22%2F_r-brtt%22%3A%22900%22%2C%22%2Fv1%2Fhas-app-brtt%22%3A%222005%22%7D ". Hb @ branch-latest.min.js:58 h @ branch-latest.min.js:59 Ib @ branch-latest.min.js:60 Z.b @ branch-latest.min.js:120 h @ branch-latest.min.js:123 (anonymous) @ branch-latest.min.js:121
do.js:7572 Fetch finished loading: GET " https://emekaokoye.solid.community/profile/card". getResource @ do.js:7572 getResourceGraph @ do.js:7651 setUserInfo @ do.js:9913 submitSignIn @ do.js:9853
do.js:7572 GET https://emekaokoye.solid.community/ 401 (Unauthorized) getResource @ do.js:7572 getResourceGraph @ do.js:7651 initBrowse @ do.js:3088 setupResourceBrowser @ do.js:3180 saveAsDocument @ do.js:3531 dd.addEventListener.e @ do.js:2331
do.js:7576 Uncaught (in promise) Error: Error fetching resource: 401 Unauthorized at _fetch.then.response (do.js:7576) _fetch.then.response @ do.js:7576 Promise.then (async) initBrowse @ do.js:3090 setupResourceBrowser @ do.js:3180 saveAsDocument @ do.js:3531 dd.addEventListener.e @ do.js:2331
do.js:7572 Fetch failed loading: GET "https://emekaokoye.solid.community/". getResource @ do.js:7572 getResourceGraph @ do.js:7651 initBrowse @ do.js:3088 setupResourceBrowser @ do.js:3180 saveAsDocument @ do.js:3531 dd.addEventListener.e @ do.js:2331
using-big-data-and-natural-language-processing-techniques-to-query-the-panama-papers-leak-4d47cc362357:1 Refused to connect to 'https://emekaokoye.solid.community/public/foo' because it violates the following Content Security Policy directive: "connect-src https://localhost https://.instapaper.com https://.stripe.com https://.paypal.com https://getpocket.com https://medium.com:443 https://. medium.com:443 https://.medium.com https://medium.com https://.medium.com https://.algolia.net https://cdn-static-1.medium.com https://dnqgz544uhbo8.cloudfront.net https://cdn-videos-1.medium.com https://cdn-audio-1.medium.com https://.lightstep.com https://.branch.io https://app.zencoder.com wss://.native.ai https://*.native.ai 'self'".
do.js:3630 Error saving document TypeError: Failed to fetch fetcher.putResource.then.catch.error @ do.js:3630 Promise.catch (async) saveAsDocument.addEventListener.e @ do.js:3629
do.js:7884 Fetch finished loading: OPTIONS " https://emekaokoye.solid.community/public/foo". putResource @ do.js:7884 saveAsDocument.addEventListener.e @ do.js:3612
On Thu, Nov 8, 2018 at 12:03 PM Sarven Capadisli [email protected] wrote:
@emekaokoye https://github.com/emekaokoye, thanks for reporting! I presume you're using the dokieli extension (from Chrome store) and not just a webpage with existing dokieli embedded.
When you say you sign in with your WebID, did you mean that you entered the URI in the Sign in dialog or did you go through the OpenID Connection authentication process (and selected your identity provider)?
Besides the authentication issue, you probably already have a folder with name public and one possible issue with what you're attempting to do is that, it is trying to create a file with the same name. AFAIK, that will not succeed that way. We can come back to this point.. so, for the time being just test with something like https://.... /public/foo
@kidehen https://github.com/kidehen, you mentioned that you had to logout/in again to make it work. Can you elaborate? I haven't experienced this issue. Is the session being cleared somehow between states? When is the exact moment that it is gone?
I certainly would like to replicate the issue.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/linkeddata/dokieli/issues/257#issuecomment-436956963, or mute the thread https://github.com/notifications/unsubscribe-auth/AAePcDuY4Rri0bWvQbIX8eWjbBGXprLNks5utA-TgaJpZM4YT91D .
-- Regards,
Emeka Okoye. Mobile: +2348023139936 (NG), +233269310862 (GH) Skype: Emx2004 Twitter: http://twitter.com/emekaokoye Linkedin: http://ng.linkedin.com/in/emekaokoye *Blog: *http://linkedopendatang.blogspot.com/ http://ng.linkedin.com/in/emekaokoye Google+: https://plus.google.com/+EmekaOkoye/about https://plus.google.com/114457961627178656743/about About Me: http://about.me/emekaokoye
@emekaokoye Thanks for the check. I meant that public is your directory and foo is a file that you want to save to. So, it souldn't be a directory. Simply just make sure that the destination it wants to save to should be a file and not a directory (double check to see if it ends with a slash). Maybe there is a bug somewhere here but let's iron this bit out. Try saving to public/bar - don't need to do anything in addition to that.
@kidehen re:
Go about my normal business
I need to confirm this but what I highly suspect that's happening is that the OIDC token is no longer valid but dokieli makes you think that you're still signed in eg. showing your avatar/name in the menu. I'll look into reissuing auth and updating the UI to reflect the 'real' state.