Is the gs:requestConsent (UMP) call working for anyone? No consent popup on device

DigiChainDigiChain Member, PRO Posts: 1,292
in Tech Support

Hi all,

I’m back in GameSalad after a couple of years to update some Android games for the new Google Play requirements (using latest the RC), and I’ve found that the Google UMP consent popup isn’t appearing.

  • My games were last published about two years ago, using the “gs:requestConsent” Tweet Sheet behaviour at the start of the game, as per the RC 2023-12-20 notes.
  • AdMob shows almost all EEA/UK impressions from those live builds as Limited ads. For one game’s latest version, that was 1,014 Limited ads vs 8 unrestricted in the UK over 30 days. That fits no consent popup ever being shown to users.
  • A GDPR message is published in AdMob and assigned to the app.
  • I’ve now tested on a device (UK, clean install): neither a fresh build nor the old games I reinstalled show a popup.
  • In Creator (1.25.103) preview, the “Social Sharing is not supported in the creator...” message appears, so the action seems to fire.

So it looks like the consent call may never have worked in these builds, not that something has recently broken. Is the consent popup working for anyone else, on any build? Is this a known bug, or is there something extra I should be doing? @adent42 , any idea whether this needs looking at?

Thanks!

Comments

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,381

    I'll need to look into it, but I remember when testing that it was hard to get the consent call to reset for the same package id so that it shows again. I had to test by using a different package id.

  • DigiChainDigiChain Member, PRO Posts: 1,292

    Thanks for looking into it.

    The reset issue might explain my test devices, but not the live data: across the UK and EEA, over 95% of my live impressions are Limited ads (e.g. UK 1,014 vs 8 unrestricted, Spain 1,589 vs 78, Germany 893 vs 51, over 30 days), so first-time users don’t seem to see the popup either. I’ll retest with a different package ID and report back.

  • DigiChainDigiChain Member, PRO Posts: 1,292

    @adent42  Quick update: I tested the live versions on two phones that have never had the game installed (different Google accounts, UK), and neither shows a consent popup. Along with the AdMob data, that suggests the consent call isn’t working for first-time users either.

    Could you look at whether gs:requestConsent actually triggers UMP in the Android build?

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,381

    Can you DM a publish link? It looks like the issue is that it won't show unless you have ad networks enabled, but I assume you do.

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,381

    Also try a re-publish. I need to test it to, but we fixed a bunch of issues so that one might have been fixed inadvertantly (I don't think so, based on tracing the code, but it might be something I missed or me pushing something I thought was already out there)

  • DigiChainDigiChain Member, PRO Posts: 1,292
    edited 1:56PM

    @adent42  - I've just republished and consent is now showing, so whatever you did seems to have fixed it. Thanks!

    However I now have a new issue when publishing to Google Play:

    Foreground service permissions

    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.


    I can't see anyway in which I can disable this permission - is this something you need to remove?

Sign In or Register to comment.

© Vanilla Keystone Theme 2026