Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

ff errors out attempting to use Apple app store link

  • 1 Antwort
  • 0 haben dieses Problem
  • 16 Aufrufe
  • Letzte Antwort von cor-el

more options

I am on linux ( ubuntu 18.04 ) while attempting to manage the iOS apple app store settings using

       https://itunes.apple.com/us/app/myappleappname/id1146173105?ls=1&mt=8

ff 61.0a1 (2018-05-03) (64-bit) shows a blank white screen with console error

           The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.

Possibly this is Apple's way of forcing people to use an OSX machine while managing their Apple app store apps ... hopefully ff can get fixed to handle this

I am on linux ( ubuntu 18.04 ) while attempting to manage the iOS apple app store settings using https://itunes.apple.com/us/app/myappleappname/id1146173105?ls=1&mt=8 ff 61.0a1 (2018-05-03) (64-bit) shows a blank white screen with console error The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature. Possibly this is Apple's way of forcing people to use an OSX machine while managing their Apple app store apps ... hopefully ff can get fixed to handle this

Alle Antworten (1)

more options

That error message about the encoding shouldn't cause this. In some cases only a few characters (likely in the x80-xff range) might be wrong, but not the whole page.

You appear to have a lot of content blocking extensions.

If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block (wanted) content (Adblock Plus, NoScript, Disconnect, Ghostery, Privacy Badger, uBlock Origin) always make sure such extensions do not block (wanted) content.

  • make sure your extensions and filters are updated to the latest version

You see the shield icon at the left end of the location/address bar in case content is blocked by Tracking Protection.

  • click the shield icon for more detail and possibly disable the protection
  • check the Web Console for more detail about what content is blocked by Tracking Protection
  • "3-bar" menu button or Tools -> Web Developer