Los tipos de servicio en primer plano son obligatorios

Para permitir que los desarrolladores sean más conscientes con la definición de los servicios en primer plano para el usuario, en Android 10, se introdujo el atributo android:foregroundServiceType dentro del elemento <service>.

Si tu app está orientada a Android 14, debe especificar los tipos correctos de servicio en primer plano. Al igual que en versiones anteriores de Android, se pueden combinar varios tipos de servicios. En esta lista, se muestran los tipos de servicios en primer plano que puedes elegir:

• camera
• connectedDevice
• dataSync
• health
• location
• mediaPlayback
• mediaProjection
• microphone
• phoneCall
• remoteMessaging
• shortService
• specialUse
• systemExempted

Si un caso de uso en tu app no está asociado con ninguno de estos tipos, te recomendamos que migres la lógica para usar WorkManager o tareas de transferencia de datos que inicia el usuario..

Los tipos health, remoteMessaging, shortService, specialUse y systemExempted son nuevos en Android 14.

En el siguiente fragmento de código, se brinda el ejemplo de una declaración de tipo de servicio en primer plano en el manifiesto:

<manifest ...>
  <uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
  <uses-permission android:name="android.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACK" />
    <application ...>
      <service
          android:name=".MyMediaPlaybackService"
          android:foregroundServiceType="mediaPlayback"
          android:exported="false">
      </service>
    </application>
</manifest>

Si una app orientada a Android 14 no define tipos para un servicio determinado en el manifiesto, el sistema generará MissingForegroundServiceTypeException cuando se llame a startForeground() para ese servicio.

Declara un nuevo permiso para usar tipos de servicio en primer plano

If apps that target Android 14 use a foreground service, they must declare a specific permission, based on the foreground service type, that Android 14 introduces. These permissions appear in the sections labeled "permission that you must declare in your manifest file" in the intended use cases and enforcement for each foreground service type section on this page.

All of the permissions are defined as normal permissions and are granted by default. Users cannot revoke these permissions.

Incluye el tipo de servicio en primer plano durante el tiempo de ejecución

The best practice for applications starting foreground services is to use the overloaded version of startForeground() where you pass in a bitwise integer of foreground service types. You can choose to pass one or more type values.

Usually, you should declare only the types required for a particular use case. This makes it easier to meet the system's expectations for each foreground service type. In cases where a foreground service is started with multiple types, then the foreground service must adhere to the platform enforcement requirements of all types.

If you start a foreground service that uses any of the following types, however, you should always include the types each time you call startForeground() for that service:

• FOREGROUND_SERVICE_TYPE_CAMERA
• FOREGROUND_SERVICE_TYPE_LOCATION
• FOREGROUND_SERVICE_TYPE_MICROPHONE

Service.startForeground(0, notification, FOREGROUND_SERVICE_TYPE_LOCATION)

If the foreground service type is not specified in the call, it will default to the values defined in the manifest.

Verificaciones del tiempo de ejecución del sistema

El sistema controla el uso adecuado de los tipos de servicios en primer plano y confirma si la app solicitó los permisos de tiempo de ejecución correspondientes o si usa las APIs requeridas. Por ejemplo, el sistema espera que las apps que usan el tipo FOREGROUND_SERVICE_TYPE_LOCATION de servicio en primer plano soliciten ACCESS_COARSE_LOCATION o ACCESS_FINE_LOCATION.

Esto implica que las apps deben seguir un orden de operaciones muy específico cuando le solicitan permisos al usuario e inician servicios en primer plano. Se deben solicitar y obtener los permisos correspondientes antes de que la app llame a startForeground(). Las apps que solicitan los permisos correctos después de que se inicia el servicio en primer plano deben cambiar este orden de operaciones y solicitar el permiso antes de iniciar el servicio en primer plano.

Los detalles de la aplicación forzosa de la plataforma aparecen en las secciones etiquetadas como "requisitos del tiempo de ejecución" en las secciones de casos de uso previstos y de aplicación forzosa de cada tipo de servicio en primer plano en esta página.

Casos de uso previstos y aplicación forzosa para cada tipo de servicio en primer plano

Para usar un tipo determinado de servicio en primer plano, debes declarar un permiso particular en tu archivo de manifiesto, además de cumplir con requisitos específicos del tiempo de ejecución. Tu app también debe cumplir con uno de los conjuntos de casos de uso previstos para ese tipo. En las siguientes secciones, se explica el permiso que debes declarar, los requisitos del tiempo de ejecución y los casos de uso previstos para cada tipo.

Cámara

Permission that you must declare in your manifest file

FOREGROUND_SERVICE_CAMERA

Runtime requirements

Request the CAMERA runtime permission

Description

Continue to access the camera from the background, such as video chat apps that allow for multi-tasking.

Dispositivo conectado

Permission that you must declare in your manifest file

FOREGROUND_SERVICE_CONNECTED_DEVICE

Runtime requirements

At least one of the following conditions must be true:

• Declare at least one of the following permissions in your manifest:

  • CHANGE_NETWORK_STATE
  • CHANGE_WIFI_STATE
  • CHANGE_WIFI_MULTICAST_STATE
  • NFC
  • TRANSMIT_IR

• Request at least one of the following runtime permissions:

  • BLUETOOTH_CONNECT
  • BLUETOOTH_ADVERTISE
  • BLUETOOTH_SCAN
  • UWB_RANGING

• Call UsbManager.requestPermission()

Description

Interactions with external devices that require a Bluetooth, NFC, IR, USB, or network connection.

Sincronización de datos

Permission that you must declare in your manifest file

FOREGROUND_SERVICE_DATA_SYNC

Runtime requirements

None

Description

Data transfer operations, such as the following:

• Data upload or download
• Backup-and-restore operations
• Import or export operations
• Fetch data
• Local file processing
• Transfer data between a device and the cloud over a network

Salud

Permission that you must declare in your manifest file

FOREGROUND_SERVICE_HEALTH

Runtime requirements

At least one of the following conditions must be true:

• Declare the HIGH_SAMPLING_RATE_SENSORS permission in your manifest.

• Request at least one of the following runtime permissions:

  • BODY_SENSORS
  • ACTIVITY_RECOGNITION

Description

Any long-running use cases to support apps in the fitness category such as exercise trackers.

Ubicación

Permission that you must declare in your manifest file

FOREGROUND_SERVICE_LOCATION

Runtime requirements

Request at least one of the following runtime permissions:

• ACCESS_COARSE_LOCATION
• ACCESS_FINE_LOCATION

Description

Long-running use cases that require location access, such as navigation and location sharing.

Contenido multimedia

Permission that you must declare in your manifest file

FOREGROUND_SERVICE_MEDIA_PLAYBACK

Runtime requirements

None

Description

Continue audio or video playback from the background. Support Digital Video Recording (DVR) functionality on Android TV.

Proyección de contenido multimedia

Permission that you must declare in your manifest file

FOREGROUND_SERVICE_MEDIA_PROJECTION

Runtime requirements

Call the createScreenCaptureIntent() method before starting the foreground service.

Description

Project content to non-primary display or external device using the MediaProjection APIs. This content doesn't have to be exclusively media content. Excludes Cast SDK.

Micrófono

Permiso que debes declarar en tu archivo de manifiesto

FOREGROUND_SERVICE_MICROPHONE

Requisitos del tiempo de ejecución

Solicita el permiso del tiempo de ejecución RECORD_AUDIO.

Descripción

Continúa con la captura de micrófono en segundo plano, como las grabadoras de voz o las apps de comunicación.

Llamada telefónica

Permission that you must declare in your manifest file

FOREGROUND_SERVICE_PHONE_CALL

Runtime requirements

At least one of the following:

• Declare the MANAGE_OWN_CALLS permission in your manifest file.
• Hold the ROLE_DIALER role.

Description

Continue an ongoing call using the ConnectionService APIs.

Mensajería remota

Permiso que debes declarar en tu archivo de manifiesto

FOREGROUND_SERVICE_REMOTE_MESSAGING

Requisitos del tiempo de ejecución

Ninguno

Descripción

Transfiere mensajes de texto de un dispositivo a otro. Brinda asistencia para la continuidad de las tareas de mensajería de un usuario cuando este cambia de dispositivo.

Servicio corto

Permission that you must declare in your manifest file

None

Runtime requirements

None

Description

Quickly finish critical work that cannot be interrupted or postponed.

This type has some unique characteristics:

• Can only run for a short period of time (about 3 minutes).
• No support for sticky foreground services.
• Cannot start other foreground services.
• Doesn't require a type-specific permission, though it still requires the FOREGROUND_SERVICE permission.
• A running foreground service cannot change to or from shortService type.

The timeout for shortService begins from the moment that Service.startForeground() is called. The app is expected to call Service.stopSelf() or Service.stopForeground() before the timeout occurs. Otherwise, the new Service.onTimeout() is called, giving apps a brief opportunity to call stopSelf() or stopForeground() to stop their service.

A short time after Service.onTimeout() is called, the app enters a cached state and is no longer considered to be in the foreground, unless the user is actively interacting with the app. A short time after the app is cached and the service has not stopped, the app receives an ANR. The ANR message mentions FOREGROUND_SERVICE_TYPE_SHORT_SERVICE. For these reasons, it's considered best practice to implement the Service.onTimeout() callback.

The Service.onTimeout() callback doesn't exist on Android 13 and lower. If the same service runs on such devices, it doesn't receive a timeout, nor does it ANR. Make sure that your service stops as soon as it finishes the processing task, even if it hasn't received the Service.onTimeout() callback yet.

It's important to note that if the timeout of the shortService is not respected, the app will ANR even if it has other valid foreground services or other app lifecycle processes running.

If an app is visible to the user or satisfies one of the exemptions that allow foreground services to be started from the background, calling Service.StartForeground() again with the FOREGROUND_SERVICE_TYPE_SHORT_SERVICE parameter extends the timeout by another 3 minutes. If the app isn't visible to the user and doesn't satisfy one of the exemptions, any attempt to start another foreground service, regardless of type, causes a ForegroundServiceStartNotAllowedException.

If a user disables battery optimization for your app, it's still affected by the timeout of shortService FGS.

If you start a foreground service that includes the shortService type and another foreground service type, the system ignores the shortService type declaration. However, the service must still adhere to the requirements of the other declared types.

Uso especial

Permission that you must declare in your manifest file

FOREGROUND_SERVICE_SPECIAL_USE

Runtime requirements

None

Description

Covers any valid foreground service use cases that aren't covered by the other foreground service types.

In addition to declaring the FOREGROUND_SERVICE_TYPE_SPECIAL_USE foreground service type, developers should declare use cases in the manifest. To do so, they specify the <property> element within the <service> element. These values and corresponding use cases are reviewed when you submit your app in the Google Play Console.

<service android:name="fooService" android:foregroundServiceType="specialUse">
  <property android:name="android.app.PROPERTY_SPECIAL_USE_FGS_SUBTYPE" android:value="foo"/>
</service>

Sistema exento

Permission that you must declare in your manifest file

FOREGROUND_SERVICE_SYSTEM_EXEMPTED

Runtime requirements

None

Description

Reserved for system applications and specific system integrations, to continue to use foreground services.

To use this type, an app must meet at least one of the following criteria:

• Device is in demo mode state
• App is a Device Owner
• App is a Profiler Owner
• Safety Apps that have the ROLE_EMERGENCY role
• Device Admin apps
• Apps holding SCHEDULE_EXACT_ALARM or USE_EXACT_ALARM permission.
• VPN apps using the VpnService (apps using PlatformVpnProfile are not eligible)

Otherwise, declaring this type causes the system to throw a ForegroundServiceTypeNotAllowedException.

Aplicación forzosa de las políticas de Google Play para usar tipos de servicios en primer plano

En los próximos meses, Google Play compartirá más detalles sobre una política que restringe cuándo y cómo tu app declara tipos de servicio en primer plano, en especial, si estos no coinciden con las expectativas del sistema.