This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Le thread ibilondoloziwe. Nceda ubuze umbuzo omtsha ukuba ufuna uncedo.

Scrolling bookmarks causes iOS app to crash

  • 2 iimpendulo
  • 2 inale ngxaki
  • 1 view
  • Impendulo yokugqibela ngu carl.graziano

carl.graziano
carl.graziano
more options

Attempted to scroll through a folder of bookmarks (Firefox for iOS on an older iPad Pro that’s been fully updated to iOS 16.1). About halfway through the scroll, the app shuts down. Upon restart, it restores tabs, but also apparently clears cache, forcing me to re-login to accounts.

Attempted to scroll through a folder of bookmarks (Firefox for iOS on an older iPad Pro that’s been fully updated to iOS 16.1). About halfway through the scroll, the app shuts down. Upon restart, it restores tabs, but also apparently clears cache, forcing me to re-login to accounts.

Isisombulu esikhethiweyo

Hi

I am sorry to hear that Firefox for iOS is crashing. I hope that we can help resolve this for you.

As a first step, close down many of the tabs that you have open to as few as possible. Does this help reduce the incidence of a crash?

If this does not help, open the iOS Settings app, find Firefox and select Clear History and Website Data. Does this help?

Failing that, we will need to look into this in more detail with some logs from inside your copy of Firefox for iOS:

  1. Launch Firefox.
  2. Open Settings.
  3. Scroll down to Version and tap it several times.
  4. Scroll down and hit "Debug: copy log files to app container". This triggers the logs to be saved into the Documents folder.
  5. Open the Files App on your iOS device and navigate to Fennec > Logs. You can see the different logs files here, which you can export using the share menu from Apple to a desktop computer.
  6. Open the file and replace any email address with XXXXXXXXX - and keep a copy of this report.
  7. Copy and past the full report into https://paste.mozilla.org/, setting the two options at the top to Plain Text and Expire in one week.
  8. Select Paste Snippet on the right hand side, then copy and past the link into a reply to this thread.

I hope that this helps.

Funda le mpendulo kwimeko leyo 👍 1

All Replies (2)

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Isisombululo esiKhethiweyo

Hi

I am sorry to hear that Firefox for iOS is crashing. I hope that we can help resolve this for you.

As a first step, close down many of the tabs that you have open to as few as possible. Does this help reduce the incidence of a crash?

If this does not help, open the iOS Settings app, find Firefox and select Clear History and Website Data. Does this help?

Failing that, we will need to look into this in more detail with some logs from inside your copy of Firefox for iOS:

  1. Launch Firefox.
  2. Open Settings.
  3. Scroll down to Version and tap it several times.
  4. Scroll down and hit "Debug: copy log files to app container". This triggers the logs to be saved into the Documents folder.
  5. Open the Files App on your iOS device and navigate to Fennec > Logs. You can see the different logs files here, which you can export using the share menu from Apple to a desktop computer.
  6. Open the file and replace any email address with XXXXXXXXX - and keep a copy of this report.
  7. Copy and past the full report into https://paste.mozilla.org/, setting the two options at the top to Plain Text and Expire in one week.
  8. Select Paste Snippet on the right hand side, then copy and past the link into a reply to this thread.

I hope that this helps.

carl.graziano
carl.graziano Umnini wombuzo
more options

Clearing history and website data seems to have fixed it. Thanks!