Ari Grant, Facebook Dev, en su cuenta de Facebook
We recently heard reports of some people experiencing battery issues with the Facebook iOS app and have been looking into the causes of these problems. We found a few key issues and have identified additional improvements, some of which are in the version of the app that was released today.
Los problemas con la App de Facebook en iOS no son nuevos. O tardaron en escuchar los reportes, o justo cuando explotó uno que mostraba como la app era responsable de consumir algo así como el 75% de la batería habiendo estado 2 minutos en pantalla y más de 50 horas en segundo plano, teniendo la opción de “Actualización en segundo plano” desactivado.
The first issue we found was a “CPU spin” in our network code. A CPU spin is like a child in a car asking, “Are we there yet? Are we there yet? Are we there yet?”with the question not resulting in any progress to reaching the destination. This repeated processing causes our app to use more battery than intended. The version released today has some improvements that should start making this better.
Un bug menos
The second issue is with how we manage audio sessions. If you leave the Facebook app after watching a video, the audio session sometimes stays open as if the app was playing audio silently. […] Our fixes will solve this audio issue and remove background audio completely.
Muchos dudan sobre si esto no era una forma que utilizaba Facebook para mantener la app corriendo y así tener más información sobre los usuarios (localización tal vez?). Y por eso salieron a aclararlo:
The issues we have found are not caused by the optional Location History feature in the Facebook app or anything related to location. If you haven’t opted into this feature by setting Location Access to Always and enabling Location History inside the app, then we aren’t accessing your device’s location in the background. The issues described above don’t change this at all.
Así que no queda otra que pensar que fué sin intención. ¯\_(ツ)_/¯
