Another Google SDK update: com.google.android.play:core

I'm receiving similar warnings, although it's not about crashes:

Update your Play Core Maven dependency to an Android 14 compatible version! Your current Play Core library is incompatible with targetSdkVersion 34 (Android 14), which introduces a backwards-incompatible change to broadcast receivers to improve user security. As a reminder, from August 31, Google Play requires all new app releases to target Android 14. Update to the latest Play Core library version dependency to avoid app crashes: Please login to see this link.

I'm receiving similar warnings,

• This version increases the minimum build to Android 5 as per the error log when I tried to build the .apk.
• It built the .apk after I changed the minimum version to 5.0.
• I got this error message from Google Play

Quote

Incomplete foreground service permission declaration

All developers requesting access to foreground service permissions introduced in Android 14 are required to complete this declaration or remove these permissions from their app's manifest

Declaration options below. As far as I know I'm not using any of these. I don't know what's declared in the manifest.

Quote

Your app uses the FOREGROUND_SERVICE_DATA_SYNC permission. You can only use this permission if your app performs tasks noticeable to the user when they're not directly interacting with your app.

Please login to see this link.

Data sync

What tasks require your app to use the FOREGROUND_SERVICE_DATA_SYNC permission?

Network processing

Backing up, restoring

Other

Local processing

Media transcoding

Importing, exporting

Other

Other tasks

Other

Display More

Extensions:

• Active Backdrop
• Android object - to set immersive mode and open URL (only if user clicks on the link)
• Android Screen Support (Not using any commands - just ticked the block under preconfigured to use all devices)
• AndroidPlus - to set layout to landscape using sensor
• Edit Box (kcedit.mfx)
• ini (kcini.mfx)
• Multiple Touch

Export:

• Build API 34
• Minimum Android 5.0
• Target 14.0

Quote from Yves

Here is a Please login to see this link. for the stand-alone version of Fusion (if you guys can test it we'll push it to Steam too). It should fix the Play Core library warnings.

If any issue, you can reinstall the Please login to see this link. of the Android runtime for the build 295.10.

Fernando

I have the same problem on Google Play, but with the Steam version of CF2.5+ Developer, Build R295.10, Nov 8 2023.

core:1.10.3

"Update your Play Core Maven dependency to an Android 14 compatible version! Your current Play Core library is incompatible with targetSdkVersion 34 (Android 14), which introduces a backwards-incompatible change to broadcast receivers to improve user security." (Build API 34, Target 14)

This info first appeared just under a week ago, before that everything was fine.

Yves

Is the quick patch already available for the Steam version?

Best regards

Quote from Fernando

i checked this situation and none of the extensions added this, but it is entirely to Google.

Please add this to RuntimeAndroid.zip and inside your rmanifest.xml, just above <!-- Permissions -->

Code

<uses-permission android:name="android.permission.FOREGROUND_SERVICE_DATA_SYNC" tools:node="remove"/>

When I change the AndroidRuntime.zip file it won't build the application. I get the error message: ...Temp\AndE5B9\app\src\main\java\Movements\CRMvt.java was not found.

The .apk will build if I use the previous unmodified AndroidRuntime.zip.

I only added in the one line using Notepad++, but I had to unzip and rezip the file to do so.

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
     xmlns:tools="http://schemas.android.com/tools"
     android:versionCode="1"
     android:versionName="1.0.0"
     android:installLocation="auto">
      
   <uses-feature android:name="android.software.leanback" android:required="false" />
    <uses-permission android:name="android.permission.FOREGROUND_SERVICE_DATA_SYNC" tools:node="remove"/>

    <!-- Permissions -->

Quote from Dobermann

I just updated a small game and i don't have any issue. It seems to have removed the warning.

I don't know if it makes a difference but i target API 13.0 while Janette4 is targeting API 14.0, everything else is the same (Build API 34 and Minimun Android 5.0).
I'm going to test another game where it targets API 14.0 and uses a lot of extensions.

The warning was also removed by me. But this new warning was fatal. You can't submit without filling in a form and pointing out which service you're using. (I think you also need to submit a video on how the user can activate or bypass the foreground service.)

Thanks Yves. Your runtime worked.

The app was accepted by Google Play without any fatal messages. It's now in review.

(There were the usual warnings, because I'm submitting an .apk / no debug symbols and nonsense like that, but nothing serious.)