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

Thanks! The patch worked for me.

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.

Nothing happens when I click the "quick patch" link. Where can I download the fix for the Google changes that must be fixed before August 31?

Forgive me for being a bitching pain BUT: it is getting a bit tiresome to have to push, ask, beg for the Android extension to be up to date with the Google requirements every time it changes. Why? We paid for it once and we have good apps/games that brings income.

The patch might be blocked by your browser.

Check your download icon - it will show you there's an issue (it's not downloaded often enough). Click the 3 dots next to it and click keep (In Edge browser).

Quote from Janette5

The patch might be blocked by your browser.

Check your download icon - it will show you there's an issue (it's not downloaded often enough). Click the 3 dots next to it and click keep (In Edge browser).

Thank you so much for the suggestion about the browser, got the file now. 😊

Unfortunately Google did not accept my update made with the patch due to the Play billing . Have no idea how to fix this.
This is their message:

"This app targets Android 14 or above and your current Play Billing Library version doesn't support Android 14. To target the latest Android version, please update your PBL version to either 5.2.1 or 6.0.1 and above."

Quote from Yves

I've sent you a PM with modified the runtime.

Hi Yves,
I am a long time clickteam customer, I had an app on google play but google has removed it from their platform because I need to update it.

I have

The DEV version of clickteam R295.10
Android export module version (cf25androidexpsetup.295.10.240124)
I use Android Studio Flamingo | 2022.2.1
SDK Build 34

Target 14

and it compiles without problem the aab file, but when uploading to google play I get this error :

"Your com.google.android.play:core:1.10.3 library is not compatible with targetSdkVersion version 34 (Android 14), which introduces a backwards-incompatible

change to broadcast receivers. As a reminder, as of 31 August 2024, Google Play will require all new app versions to target Android 14. Please update to the latest library version dependency to avoid app crashes.

It is important for me to republish the app is company."

Please could you give me a solution or a detailed explanation of how to compile for android currently?
Thank you very much.

Quote from dropsonteam

Please could you give me a solution or a detailed explanation of how to compile for android currently?
Thank you very much.

There's a patch . Download and install it. Then rebuild and resubmit your App like you did before.

Thread

Update for the Play Billing Library version and Play Core Maven dependency

Here is a patch for both the standalone and Steam versions of the Android runtime. This is a hotfix that addresses two important issues that you may encounter in the Google Play Console, the outdated Google Play Billing Library version and the Play Core Maven dependency.

Standalone: Please login to see this link.

Steam:
1. Open the Fusion settings in the Steam client
2. Select the Betas tab
3. Enter the following password: xyz555pbx444 and click the "Participate to the "androidinapp295update -…

Olivier

September 3, 2024 at 9:59 AM

thank you very much Janette5, I have installed the patch, I have compiled with the API34, and target v14, a minimum v5. I have sent it to the google platform and finally passed to revision.
Thank you very much for your message

Issue with Google Play Data Safety Policy Rejection

Hi everyone,

I compiled an Android app using Clickteam Fusion with the Android export module. In the Fusion settings, I pointed the JDK and SDK directories to those in Android Studio. My app does not collect any user data, so I did not request any permissions in the app.

I used API Level 34 with a target version of 14 and a minimum version of 5. The app compiled successfully, and Google Play Console did not flag any errors during the upload. However, during the review process, my app was rejected for the following reason:

Rejection Reason:

Quote

Policy Declaration - Data Safety Section: Device Or Other IDs Data Type

Google states that the app may access Device IDs such as Advertising ID, Android ID, IMEI, etc., even though I have not implemented anything that collects such data.

Google has asked me to either:

1. Update the Data Safety section in Play Console to declare the collection of these IDs, or
2. Remove any code or functionality accessing these identifiers.

I’m not sure how or why these identifiers are being accessed, as my app does not explicitly require or collect them. Could this be caused by libraries or components in the Clickteam Fusion export module?

Has anyone else faced this issue? Any guidance on how to resolve this would be much appreciated!

Thank you in advance!

Hi Olivier

Thank you so much for your detailed response and the helpful link! I hadn’t considered that the Google Play Games extensions might be the source of the issue. It makes sense now that data like Device or Other IDs would need to be disclosed if the app uses services like achievements or score submissions.

I’ll review the Please login to see this link. page you shared and update my app’s Data Safety form accordingly. Your explanation has given me a much clearer understanding of how to proceed.

Thanks again for your support! It’s great to have such a helpful community. 😊