![Firefox vir iOS logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-37-48-1aeaf0_1.png)
Constant crashes when syncing enabled on Firefox app for iOS
I am experiencing constant crashes while using Firefox app for iOS. The error message is the standard “Well this is embarrassing” message with no additional context. It appears to be occurring when sync is enabled - when I have it disabled I don’t experience any crashes, or at least so infrequently that I don’t notice it. While syncing is enabled however it crashes no matter what I am doing at the time, and as frequently as every couple minutes. The version in settings is Firefox daylight 102.1. I have uninstalled and reinstalled a couple times but the issues persists.
Gekose oplossing
rschletty said
Thank you. I am looking forward to an update.
This hasn't been fixed the last time I checked. But we released a new version recently. Have you tried update and see if the issue is still reproducible?
Lees dié antwoord in konteks 👍 0All Replies (11)
Hi Conner,
Thanks for reporting here. Our team is currently investigating this type of crash. Would you be able to try find the crash logs from the Analytics menu in the iOS settings app and share it to us?
Here is an incident from earlier
Thanks, Conner! I've sent it to our engineering team to investigate further. I'll make sure to ping you when we have a resolution.
I reported crashes with iOS Firefox. Mozilla Support sent me an email reply but I can't find it now. I am glad I found this forum thread.
I am convinced that syncing iOS with two Mac desktop installations of Firefox is the culprit. I turned off sync on all devices and iOS Firefox does not crash now on my iPhone.
The latest versions of Firefox are running in the following environments: – iOS 15.5 on an iPhone 13 Pro Max (128 GB) – macOS Mojave on a 2016 MacBook Pro (16 GB) – macOS High Sierra on a 2009 Mac Pro (48 GB)
Hi rschletty,
The issue is still under investigation. I'm currently following up with the team on when can we expect the fix will land for this. I'll make sure to update the thread once we have more info.
Thank you. I am looking forward to an update.
Gekose oplossing
rschletty said
Thank you. I am looking forward to an update.
This hasn't been fixed the last time I checked. But we released a new version recently. Have you tried update and see if the issue is still reproducible?
Kiki said
rschletty said
Thank you. I am looking forward to an update.This hasn't been fixed the last time I checked. But we released a new version recently. Have you tried update and see if the issue is still reproducible?
Not sure when the new version was released, but I enabled syncing again maybe about a week ago and haven’t had any crashes since. Seems to be resolved for me. Thank you and give thanks to the team
Conner said
Not sure when the new version was released, but I enabled syncing again maybe about a week ago and haven’t had any crashes since. Seems to be resolved for me. Thank you and give thanks to the team
I'm glad to hear that. (:
Gewysig op
Well, that's nice if the sync issue is fixed. But frankly, I have just about given up on Mac Firefox (reluctantly) and am starting to return to Google Chrome (which no longer supports the iPassword 6 extension).
I am reporting a terrible problem in another thread. Mac Firefox randomly shows gibberish characters for some fonts like Helvetica Neue, especially after a Firefox update. I have excellent font management with Extensis Suitcase Fusion. Sometime emptying the font cache with reboot solves the problem. Sometimes flushing web cache solves it. Sometimes I delete the Firefox app and reinstall an older version, whereupon it wants me to start over from scratch with my Firefox profile. This is frustrating. I hope the gibberish font issue is solved in the other support thread.
Sorry, I don't mean to hijack this thread. I am just saying that Firefox Profile syncing is problematic for more than one reason. No such troubles with Google Profile syncing.
Gewysig op
Hi rschletty,
Please open a new thread if you wish to follow up on the above issue. I'll lock this thread since the initial issue has been resolved.