fredriksthlm's Forum Posts

  • When the app is initialising I can see this in the logcat, seems like you are running some of your old code? I don't know what is going on, but htis looks really wrong:

    It seems from the above printscreen that you still have remaining code to validate "personalisation" which now should be obsolete.

  • First of all, thank you for finally working on this one.

    A few comments

    1)

    I've highlighted in several old forum posts that the new concent is a "breaking change" compared to the old one. I suggested to create a new plugin and deprecate the old one. Now it is somehow "a bit" updated, but a mix of the old and new.. I don't know how this should be handled now. But at the moment the ConsentStatus doesn't work at all.

    In the previous SDK you could get:

    • ConsentStatus.PERSONALIZED
    • ConsentStatus.NON_PERSONALIZED
    • ConsentStatus.UNKNOWN

    But in the new google consent you can get

    • (ConsentStatus.UNKNOWN: Unknown consent status.)
    • ConsentStatus.REQUIRED: User consent required but not yet obtained.
    • ConsentStatus.NOT_REQUIRED: User consent not required. For example, the user is not in the EEA or the UK.
    • ConsentStatus.OBTAINED : User consent obtained. Personalization not defined.

    In the plugin at the moment it seems like this doesn't work. When I'm opening my app I get the ConsentStatus "PERSONALIZED" now. This is incorrect, this status does not exist in the SDK and we need to be able to validate the correct ones. When opening the app in EU we should get REQUIRED, and opening the app elsewhere it should be NOT REQUIRED. This is needed to validate if we should show consent window or not.

    When I use the event to show to consent window the ConsentStatus changes to UNKNOWN(??)

    (I understand you might ned to keep the old stuff to not make old projects crash, but at the moment the plugin doesn't really work)

    2)

    I cannot get the condition for validating the EEA to work? Have you verified and tested this condition in the new plugin? (For me it seems to be EEA regardless of the location)

    3)

    I cannot get the ConsentForm to show. I can see in logcat that "getFormStatus" is triggered at startup, but it doesn't show when I use "Show user consent dialog", and not when I set EEA in the properties either. Do you still support to automatically open the consent screen with the properties, or should we always use the "Show.." event now? Regardless, I cannot get any of them to work. (Yes I have Funding Choices set up, and have verified this with other users as well)

    4)

    I think it would be great if you could add the action to reset the consent (this is good for testing, but also for production to let users reset their choice). It is missing in your C3plugin. github.com/admob-plus/admob-plus/blob/4e72049/packages/cordova-consent/ts/index.ts

    5)

    When checking logcat it seems you are calling get getConsentStatus twice every time used (on loading plugin, every time you load an ad etc). Is this correctly implemented? Maybe it just looks odd in the logs.. :)

    6)

    I know you/Scirra did not build this plugin yourself and I really hope you paid Ratson well for using his plugin! :) Even though it's open source. The project needs funding.

  • Not needed. See the post from Diego.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • There are three possibilities:

    1. Remove the cordova splash plugin totally

    2. Use a fork of the cordova splash plugin (https://github.com/prageeth/cordova-plugin-splashscreen)

    3. Amend the splashplugin code (easiest in Android Studio, but can also be done manually in the files before you build with the CLI)

    If you are building small projects (that loads fast) it is safe to just remove the plugin entirely from your project. If you are creating more heavy projects that takes some time to load, you should use the splash plugin but with amended code. Solution 2 and three are the same, but the forked plugin is already adjusted the code, while in solution3 you do the same manually in your project.

  • I understood you fine, but you said you went back to old version of the software instead of actually verifying the setting. It's always better to track down the root cause.

    Just out of curiosity, which version of webview do you use?

    do you have any 3rd party plugins?

  • If you believe it's due to worker mode, just turn it off again and test..

  • Thanks Ashley.

    This is what you recommend for C3 plugin makers: "I think there is some level of responsibility for addon developers to keep an eye on developer news, release notes, listen to feedback coming from users, and maybe do a quick test every couple of months". Actually you also said that you gave a heads up three months before a breaking change to C3 plugin makers to fix their plugins when you did breaking changes.

    But to be fair, Google gave you one year for this one. You also have the same responsibility to look into the release notes from Google every now and then, just to check if some small tweak is needed. Now when you didn't do anything for a year I understand it's a huge job to do it all in one go. But the UMP was really released July 2020, same time they marked the old EU consent to be deprecated.

    "If nobody is developing an addon, it will probably break sooner or later.". They also gave out a guide how to amend the ad methods to comply with v20 release (several months before removing the old methods!), but you didn't amend those either. So then the plugin broke..

    I know you are a small team and all, but unfortunately this plugin needs proper attention. You seem more interested in building your 3D boxes and such at the moment, but that is just not a good priority at the current state.

    Maybe the Admob plugin would be a good one to have external help with? Maybe consult Iain or some plugin maker to write the first version. But you must have ownership, and interest in it.

    But good that this finally seems to get proper attention. Thanks!

    My suggestion is a new one, and deprecate the old one (so it cannot be imported in any new project), but for old existing projects you should be able to maybe have them both, so you can amend the events before removing the old one. Obviously only have the new one when you export! But since it will be many breaking changes I think i will be hard to rewrite the current one to get all ACEs to work with the new stuff. (But do like you did with Function-plugin sort of).

    Good luck! Looking forward to it.

  • The entire SDK is deprecated, and no longer maintaned by Google.

    developers.google.com/admob/android/eu-consent

  • I've highlighted this many times, in several threads already. The old EU consent has been marked with a red warning text in the Google reference docs for almost a year now.

    The UMP should be used instead. It was released in July 2020.

  • I updated my phone to 14.6 now and tried my C3 app, which was released previously. No issues.

  • It is still in beta. But should be stable to use now, since it has been available since 19.4 and Admob now is on 20.1

    I saw that Ratson just implemented it to the cordova plugin AdmobPlus now.

  • just put Request IDFA at start of first layout. it will automatically only trigger for iOs. and only trigger once, unless the user reset the app.

    So remove all your events like those you have.

  • You are showing the consent screen (to show personal ads), they ask you about the ATT/IDFA request. These are not related.

  • Yes, I can confirm, that this popup shows up (the German/English mixture is really ugly by the way).

    I think you can define the english part yourself, it is a text string you can set in xcode. the german part is defined by Apple, and is shown in the iOS langauge of the phone.

  • it was a requirement (before) that you could only create instances of an object if the object already existed.