Webkitblobresource ошибка 1 что это

iPad Pro Wi-Fi,

iOS 12

Posted on Oct 3, 2018 2:43 AM

Similar questions

• As of today, my Safari on all of my IOS devices is totally non functional.
  As stated, my Safari browser is non functional on both of my IOS devices. One device is an iphone 13 pro max and the other device is the latest version of the IPAD PRO MAX 13 “.

  I have deleted Safari as an app, then in trying to re download it, I get an error message that says that it is already downloaded when it fact it is NOT.

  Please advise. I am also hearing impaired.

  Best,

  Erik

  [Personal Information Edited by Moderator]
  

  64
  2
  

• Safari won’t open Google maps
   Using iOS 14.3 on my iPad Air 2.  If I search for a destination with Safari, and then I tap on a map that shows up, the google map crashes, reloads and crashes again. Then I get the message: «A repeated error has occurred.» The same thing happens if I use Safari to go to google.com and then click on the map icon. This started happening after updating to OS 14.3.
  I have no other apps open when on Safari, and I just cleared all my storage and history. 
  I have posted this problem on the Google community support site. Lots of other people are having this problem since updating to any version of iOS 14.  The consistent reply from the Google experts is that «this is most likely a safari / ipad os 14.x issue.»
  Is Apple addressing this problem?
  

  368
  2
  

• Safari users report problems downloading pdf files
  Recently, Safari users (Mac, ipad, iphone) have not been able to download or view pdf files generated for them by my site. This always worked before with Safari, but I don’t know when the problem started. Chrome, Edge, Brave, and Firefox all work fine, but Safari gives the error: [Safari cannot open the page. The error was: «cannot parse response».] My customers use a Mac or iPad, but I verified the problem via an iphone running IOS 14.4. I have searched the web for answers and have tried deleting cached files and cookies and even disabling experimental Safari features one-by-one. So far, nothing helps. I currently tell people to use Chrome, Brave, Firefox, or Edge, but I would rather not have to do that. Any insights will be appreciated.
  

  1552
  1
  

New issue

Comments

    <PDFViewer style={{ height: '100%' }}>
      <Document>
        <Page size="A4" style={PDFStyles.page}>
          <View style={PDFStyles.section}>
             [Content]
          </View>
        </Page>
      </Document>
    </PDFViewer>

Created attachment 351778 [details]
Download methods

Overview:
In our webapp construct 3 users can download a copy of their project. When saving projects are serialized into a blob ( zip format ) on the client side. To download the file we create a Blob URL, attach it to a new HTMLAnchorElement, specify the "download" attribute as the file name ( "myproject.c3p" ) and use the HTMLElement.prototype.click function. This method works correctly in Safari 11 and in chrome. However, now it opens a new tab displaying a WebKitBlobResource error 1 and no further information.

I think this may be related to the content blocker. On the first attempt to repeat this a "popup blocked" error will appear in the address bar and allowing it will download and unzip the project into a folder called "unknown" ( which I consider broken also ). Subsequent attempts will display the WebkitBlobResource error.

I have attempted to create a simple replication for this, but even when copying the exact code into a new document and calling in the same fashion ( the development tools REPL ) it only repeats in the actual web application.

I have included the download methods, but it's fairly standard stuff.

Steps to reproduce:
1. Visit https://editor.construct.net
2. Select "new project"
3. Select "menu > project > save as > download a copy"
4. Select "ok" ( uses default name )
5. Allow popup
6. Observe "unknown" folder appearing in downloads folder
7. Repeat steps 2 - 4
8. Observe error tab

Actual results:
A new tab displaying the error: Safari can't open the page "blob:https://editor.construct.net/[ blob id ]". The error is: "The operation couldn't be completed. (WebkitBlobResource error 1.)" (WebkitBlobResource:1)

Expected Results:
A new file in the downloads folder called "New project.c3p"

Comment 2

Chris Dumez

2018-10-09 09:43:43 PDT

Issue seems to come from the fact that target=_blank is used:
1. This triggers Safari's popup blocker. If you allow the popup later on, the filename is wrong because Safari does not know about the download attribute.
2. If popups are allowed, WebKit tries to *load* the blob instead of *downloading* it, thus the network error. This is due to a bug in our createNewWindow code path which I will fix.

Comment 4

Chris Dumez

2018-10-09 10:00:25 PDT

In a follow-up, I will look into ignoring the target when the download attribute is present. The HTML spec says to download the hyperlink instead of following the hyperlink. Only the "following the hyperlink" algorithm checks the frame name.

Comment 6

Ashley Gullen

2018-10-09 10:20:45 PDT

Ah, thanks for the tip about target=_blank - setting target=_self on any download attribute links seems to work around it. We'll ship this workaround soon so to continue reproducing the issue use the following link which will use a specific version of our PWA: https://editor.construct.net/r121/

Comment 8

Chris Dumez

2018-10-09 10:45:05 PDT

(In reply to Ashley Gullen from comment #6)
> Ah, thanks for the tip about target=_blank - setting target=_self on any
> download attribute links seems to work around it. We'll ship this workaround
> soon so to continue reproducing the issue use the following link which will
> use a specific version of our PWA: https://editor.construct.net/r121/

Great, thanks.

Comment 10

WebKit Commit Bot

2018-10-09 11:25:41 PDT

All reviewed patches have been landed.  Closing bug.

Comment 11

Chris Dumez

2018-10-09 12:37:43 PDT

Follow-up to avoid Safari's popup blocking at Bug 190408.

Comment 12

Michaela Merz

2019-04-30 10:39:01 PDT

Unfortunately - it's not fixed. We are running into the same problem. A blob is assembled in Javascript, it's set into a download-URL with download attribute and it can be downloaded with Chrome, Firefox and Epiphany (webkit2gtk-4.0). We are not using frames, there's no difference with target="_self" or no target attribute, the error appears regardless of Content-Security-Settings and there is no warning or error on the console. 

Safari just opens a new tab and displays the "WebKitBlobResource error 1.). It worked fine in previous versions of Safari (on MacOS). 

Copying the generated BLOB:url into safari's URL bar allows the download of the data. 

Safari Version 12.1 (14607.1.40.1.4)

Comment 13

Ashley Gullen

2019-04-30 11:08:36 PDT

You should probably file a new issue for that, it sounds different to this one if the target doesn't affect it.

Comment 14

Michaela Merz

2019-04-30 11:12:50 PDT

It seems to be related as it behaves exactly like the original bug as posted. Only difference: We are not using iframe and target attributes. We tried with target="_self" but that didn't influence the bug. Safari just opens a new tab and displays the error.

Comment 15

Michaela Merz

2019-04-30 11:54:36 PDT

Here's an update to the bug:

Test on Image in blob.

I can .. right click open the context-menu for a blob URL and 

.. Open in new tab: Displays Image
.. Open in new page: Displays Image 
.. Download: Downloads  the image

The *only* bug is that Safari opens a new tab after clicking the "a href" and displays the WebKitBlobResource error 1. It completely ignores the download attribute (for this blob) and it opens a new tab for now reason.

Comment 16

Ashley Gullen

2019-04-30 12:53:17 PDT

I really think you should file a new issue. This is a closed issue and people tend to stop looking at them once they're marked fixed. And it's entirely possible there are two separate problems with similar looking symptoms.

Comment 17

Chris Dumez

2019-04-30 14:13:20 PDT

(In reply to Ashley Gullen from comment #16)
> I really think you should file a new issue. This is a closed issue and
> people tend to stop looking at them once they're marked fixed. And it's
> entirely possible there are two separate problems with similar looking
> symptoms.

Yes, please file a new bug with your repro steps and cc me.

Comment 19

Andy Schmidt

2020-05-01 11:04:48 PDT

(In reply to Chris Dumez from comment #17)
> (In reply to Ashley Gullen from comment #16)
> > I really think you should file a new issue. This is a closed issue and
> > people tend to stop looking at them once they're marked fixed. And it's
> > entirely possible there are two separate problems with similar looking
> > symptoms.
> 
> Yes, please file a new bug with your repro steps and cc me.

New bug created for the never-fixed additional circumstances:
https://bugs.webkit.org/show_bug.cgi?id=211234

Still happening as recent as Safari 13.1 on iOS 13.4.

Comment 20

ihar.suvorau

2021-06-28 08:03:51 PDT

The issues is still relevant in Safari 14.2, WebKit 16612.1.17.10.5 and Version 14.1.1 (16611.2.7.1.4) on macOS 11.4 (20F71).

The workaround to create a workable link was to add the "download" attribute to a-tag: 

<a href=blobURL download=file.name>text</a>

In that way Safari downloads a file without following the link.