Safari bug prompt persists in all browsers on iOS

[microbit-mark]

https://support.microbit.org/a/tickets/37316

Bug Description

Hitting download of a Hex or Python file on iOS causes the Safari bug pop up to appear, regardless of the browser used.

How To Reproduce

Steps to reproduce the behaviour:

1. On iOS in Chrome, Firefox or Safari Go to 'python.microbit.org'
2. Click on 'download'
3. See error

Expected behaviour

This should work without error as in Chrome or Firefox on the desktop.

Additional context

Asking for browser User Agent reports:

If iOS always reports that it is using Safari to the Python Editor this can be a confusing experience when using other browsers and users cannot download files.

[microbit-carlos]

@microbit-mark can you confirm that the files are not downloaded in iOS?
Normally the error is there just to indicate a bug on the filename, but the file should be downloaded correctly.
If the fail doesn't download, could we also check that it is not being blocked by a pop-up blocker? The workaround of the name issue opens the file a new tab.

[microbit-mark]

@microbit-carlos This no longer reproduces for me. Safari works as expected and does not report the error. Chrome does not report the error.

However, another issue presents itself. Using the Chrome app 87.0.4280.77, clicking on Download has no response, the file is not found in the iOS Files folder.

Clicking on connect shows the message that WebUSB is not supported

ios-chrome-issue.mov

[microbit-carlos]

Yes, thanks trying to replicate Mark.
We are investigating the download button not working on a different issue.
On my devices the download button does work on Safari though.
Did you try Firefox as well?

[microbit-mark]

Did you try Firefox as well?

Yes, the pop-up no longer appears in Firefox, but the download issue does replicate

On my devices the download button does work on Safari though.

This works for me too

[microbit-carlos]

Okay, the prompt is meant to happen with any iOS device version below 10 (so last updated before 2016).
the download file issue will be tracked as part of #367