fredriksthlm's Forum Posts

  • 7.4.2 is the current supported one by Cordova, with Cordova Android 11.

    Here is the current versions of all you need: cordova.apache.org/announcements/2022/07/12/cordova-android-release-11.0.0.html

    Construct updated to the new cordova version in the latest beta.

  • > I meant my super old ticket, which we re-opened last week. It is not related to any new changes, it is an old issue since we started with adaptives.

    This isn't anything to do with splash screens though is it? I'm not sure why you brought it up in the context of the new splash screen support?

    Sorry for confusion, no not related to the splashscreen.

    (Just that I remembered it now when I looked into the config.xml for the splash setup, since the issue with the icon is one of the reasons that we need to amend config.xml everytime before creating the project with the cli, since it doesn't get created correctly otherwise).

    but again, sorry for mixing it up.

    Thanks for the updates!

  • Thanks for looking into! Thanks for api32.

    Removing these is a bit tricky: ShowSplashScreenSpinner is still documented as affecting iOS, and SplashMaintainAspectRatio still applies for legacy Android builds. I've removed the latter from the latest builds though as it is indeed no longer a documented property.

    Ah ok, no problem. I thought you created different config files depending on if the user did an ios or android cordova export.

    > Also as mentioned in the bug tracker, the icon is not handled correctly at the moment, but there is an easy fix for it.

    I don't see a report for this, and it looked OK in my testing. Did you mean to file an issue?

    I meant my super old ticket, which we re-opened last week. It is not related to any new changes, it is an old issue since we started with adaptives. I can verify that the fix I wrote last week will solve the issue with the fallback icon for old devices. (You should just add the src tag to the adaptive icon line and map it to the icon file in c3, then it will work correct on all devices)

    github.com/Scirra/Construct-3-bugs/issues/4689

    > Also, would it be possible to format the config.xml file?

    I didn't realise it wasn't formatted! I always looked at it in an auto-formatting tool. I added formatting for the next beta.

    Haha! wow thanks, glad it was so simple. Been thinking of filing this as a bug for so long time, since I've been struggeling with this for years :D

    > Also, any particular reason you still have a config.json?

    That's used by the build service.

    Ah cool, didn't know. I always just delete it, since I don't use it in cordova.

  • Great, thanks for the release today Ashley!

    Actually you can already raise the target to 32 (which is actually the default one by cordova now). api32 is also android 12 (12S), and there are no new functionalities you need to cater for.

    regarding the new splash, since you have dedicated exports for android and ios I think you now should remove these lines form the android config.xml file:

    • ShowSplashScreenSpinner
    • SplashMaintainAspectRatio

    Also it would be handy if you added these lines to the config.xml (even though you do not need em to be mapped from C3 editor in any way, but for people doing manually builds we often want to amend these, but you can populate them with default values):

    • FadeSplashScreen (true)
    • FadeSplashScreenDuration (500)

    Also as mentioned in the bug tracker, the icon is not handled correctly at the moment, but there is an easy fix for it.

    Also, would it be possible to format the config.xml file? it is very annoying to modify it when it comes from construct, since there is no formatting or line breaks. (standard config.xml from cordova is easily readable and standard xml formatted.)

    Also, any particular reason you still have a config.json?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • When you run the project in a browser and look into the console the error message is not from Admob, it is from Adsense.

    I think you have misunderstood how the ads are working.

    You can never test Admob ad implementation in the browser.

    I would guess the reason for your Admob only works in debug and not in production is due to errouneosly set up of UMP/funding choices.

  • Construct currently use a cordova plugin that uses admob sdk 20.3.0.

    It is though not the latest version.

    If you know how to use cordova cli or Android Studio, you can easily change versions yourself

  • It will be released today Ashley.

    github.com/apache/cordova-android/blob/master/RELEASENOTES.md

    I think you should change to this new cordova version and bump api, on the first new beta on the new beta cycle. There is a few things you also need to amend for the config file, to use the new native splash. but should be minor things. (They support 32 directly now, from 30.)

    And you will need to update quite a few things on your build server I guess.

  • I believe that error message is from UMP and not for Admob actually, verify your messages and setup in Funding choices/Privacy messages. You need to have this activated for your app.

    Also note that Publisher ID is not for Admob, it is for Google Adsense/ web ads.

  • No, I don't think you need to be able to show the message again within the app.

    If the user want to make another choice, they can go into app settings on their phone and press delete app data (delete cache), this will delete their cookie and the popup will automatically show for them next time they will start the app again. You can test this yourself as well. This is handled by the ad sdk and you will not need to handle it.

  • 1: The GDPR buttons says: "Tap "Allow" on the next screen to give permission"

    but when pressed it does not go to the next screen. The examples I have seen in other apps have a screen with a bunch of options. Even when I disable the IDFA the GDPR does not go to next screen. Is this a screen I need to make?

    This is totally incorrect. You describe the IDFA explainer.

    This is not related to the GDPR. It is shown before the ATT outside EEA.

    2. Once the GDPR button is pressed the IDFA popups up. Blocking the GDPR. When an IDFA button is pressed the GDPR and IDFA disappear.

    You describe the IDFA explainer which is shown before the ATT request.

    This is not related to GDPR.

    3. Does anyone know if under the GDPR I need to provide the user with an option to later change their GDPR? For instance, do I need to put a button in settings that will bring up the GDPR screen?

    Two important notes.

    It seems you have not set up the GDPR message at all? You must create this message yourself, in funding choices.

    IDFA for iOS is not related to the european GDPR regulations. This is two different things and also handled differently in your events.

    First you need to create all your messages in UMP

  • Cordova is 11.0.0 (this is the version of the CLI)

    Cordova Android is latest stable 10.1.2 (The upcoming 11.0 release will have official support for API 31 & 32)

    But yes, you can of course target which ever api version you like, but Cordova do not officially support it yet

  • Cordova Android 11, which will support API 31 is not released yet. Still no official support for API 31 in Cordova Android 10.

    The next release will support API 31 and also API 32. But there are still few minor things to fix before the release.

    If you build with the CLI you can use the nightly build.

    You can follow the release here:

    github.com/apache/cordova-android/projects/3

    You can change API target yourself, but it might not work if you use the old Cordova.

  • Seems to be your "Event group: Level_1_Sheet / Mechanics" that suddenly started to be heavy.

    Do you have any specific events there? There was some change for movements in the recent release..?

  • there is a limit and a quota, you are also not allowed to have it on a button.

    I believe you should read the guidelines before adding the feature

    developer.android.com/guide/playcore/in-app-review

  • I use the prompt to let users set their username.

    cordova.apache.org/docs/en/11.x/reference/cordova-plugin-dialogs

    I've modified the file so the appearance match the appCompat theme and follow the google guidelines.

    Works perfectly always.