Facebook Cuts iOS Crash Rate by 50%
Now, many people are already aware of the popular networking site i.e Facebook since its the most commonly used networking site all over the world. For the past few years, its been a global phenomenon. It has been a mean for people not to just connect with each others, but it has changed many lives as well. And due to modern advancement of technology, many people are able to use it in mobile devices. Due to such emergence of iPhone and Samsung smartphone devices, many people find it comfortable to use Facebook app in mobile. But many users have complained that they find it annoying to use Facebook via mobile because it becomes slow and sometimes face different problems.
Facebook is putting more time and resources into to making sure its main app isn’t as buggy for users as it was in the past, since many people are found browsing Facebook via their mobile devices. According to the company, its New York-based team of mobile engineers have been able to cut the crash rate on iOS by 50% over the past several weeks after catching a long-term bug that was messing with the app.
With the announcement, the company has decided to encourage the Facebook Messenger App alone just to send the messages so that they can remove the feature of sending messages through the main Facebook App. This decision has faced a lot of heavy criticism from the people worldwide.
Facebook worte in a blog post that one of the biggest challenges for mobile involves debugging. It received notifications of crashes in its report analyzer, but it took months to figure out the right angle to approach the longtime issue.
The iOS issue involved two systems that were writing code to the same location — one was an expired number that happened to be the same as the new system’s location number.
“Since we are using APIs developed in the ’70s, there are no checks that our code owns this number, which allowed this bug to remain unchecked,” Spiegelberg said. “This would normally be an easy problem to diagnose with a small program, but there are multiple layers of code and hundreds of systems interacting, so searching through the interacting systems required unique diagnosis and it’s own code to algorithmically search through.”
“It turns out that abandoning manual code analysis was a good strategy,” Facebook wrote in the blog post. “The bug surfaced with existing code that was exercised more as we ramped up default secure connections for all our users.”Previous Next