Just today, news comes in that the Pixel 3 is experiencing another camera bug. This is not a stuff for everyone on the Pixel 3, but for some owners of Google’s Android flagship. It is regarding what some have called an annoying crash.
The Pixel 3 and Pixel 3 XL’s camera technology, especially the one for Night Sight is one of the most loved features in the device. However, no matter how much love and affection people have doled on it, it is not just doing fine the way it should.
One annoying bug affects how the Pixel 3 and Pixel 3 XL saves photos. This issue gets device owners frustrated to find the photos they snapped were not saved to camera roll, despite all the evidence that these pictures were actually snapped.
In other cases, the camera may just crash and users are left utterly disappointed. Pixel 3 and 3 XL users have gone on board Google for a to complain about some of the problems that they are having. Some have also gone on Reddit to complain as well. There are users who claim that third-party apps which also use the camera have encountered unexpected fatal errors when opening. This in turn affects adversely, the Pixel 3 camera app itself.
A number of apps make use of the camera and that makes the issue a considerable one. Facebook, Instagram and other social media web portals rely on the camera for their in-app photo and video sharing via internet. Also, messaging apps can integrate camera functionality so that users can share new media without having to switch to different app at first.
Other apps indirectly working with the camera or those not even working with it could become impacted negatively somehow, compounding the problem. Business apps, such as banking apps can easily fall into this category. When trying to do mobile check deposits, the user may get a fatal error message and that could a camera problem.
Google has agreed that this is its fault. In a BuzzFeed statement, the company said that it has looked into the problem and has identified a fix that will roll out in the coming weeks leading to December 2018. The company did not give a reason for the bug.
