fredriksthlm's Forum Posts

  • You cannot build anything if you don't have a working project/app and obviously it failed to import.

    It clearly states that you should read your logs to find out why it fails.

  • It is not possible to turn off antialiasing for text :(

  • you just click Build apk in the menu..? (or build signed apk if that's what you want)

  • if you use adaptive try to only have 512px in your project. the rest will be created. then you must have a fallback icon (when adaptive is not supported). unfortunately there is a bug in the cordova icon thingy that creates the wrong fallback icon.. so you have to amend it manually.

    see my bug report:

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

    you can also create all icons manually directly in android studio, developer.android.com/studio/write/image-asset-studio

  • Both the IAP and ad plugins are maintained and should be up-to-date

    It is a bit surprisingly to read this statement to be honest.

    Regarding IAP. There has been bug fixes for the Google Billing Library in v3.0.1 (released 2020-09-30) and also in v3.0.3 (released 2021-03-12) which both could affect cordova builds afaik. The Scirra IAP plugin uses v3.0.0 of the Google Billing library. (I believe this should be easy to just update.)

    Regarding consent SDK (part of Mobile Advert plugin) there has been a lot of changes here, the one which is part of the Scirra Mobile Advert is classified as "Deprecated", and is actually marked with a red warning text on the Google dev pages that is is deprecated and is no longer even maintained, at all. It does not comply with the actual regulations and should not be used. Google has released their UMP SDK a long time ago, which is the one to use now.

    Regarding Admob SDK (also part of the Mobile Advert plugin) Google has made a lot of changes for the different ads, most of which was released in v19.2-19.7. Even if your plugin has used the latest SDK you have not updated to the latest methods. It was in the release of v20 that Google finally removed the old deprecated ads, which basically made the Mobile Advert to fail totally..

    Google had released documentation how to prepare for the v20 update, which was obviously not implemented by Scirra.

    To state that your use of any of these three SDKs are "up-to-date" is just not correct.

    (Edit: And there has been just as many changes for the iOS SDKs as for the Android ones mentioned above)

  • Unfortunately there doesn't seem like any progress on this, that's why people have forked it and amended it

  • you build with cordova cli or with android studio. and remove or amend the splashscreen plugin, then it will work correctly.

    Unfortunately it's a bug in that plugin.

  • The only problem I have now is that the device closes down the app when I use the "back gesture".

    It is a cordova bug that makes the back-button terminate the app. The only way around it is to build with a fork of the splashscreen plugin, or to build with the regular plugin but comment out one line in the code or to remove the splash plugin totally from your project.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Downgrade the ad version and it will work again

    (right click on 'app' > 'Open Module Settings' > 'Dependencies', set requested Version to 19.8.0 for play-services-ads)

  • there is a method removeAllCookies to clear cookies so should be possible.

    also seems to exist a lot of different cordova plugins for clearing cookies, so just search for it. you will though need to build with the cli or android studio

  • Rex left the community for more than three years ago.

  • I guess the Google UMP will be part of the new Advert plugin.

    But to create some own framework for this doesn't seem like a good idea, since it is complicated laws and directives which are constantly changing.

  • The EU documents doesn't really state "cookies" specifically. HTML5 Local Storage is the same as using cookies. What matter is the purpose of the data to save. Only tecjnically "necessary" data is allowed to save without consent.

    Basicallt this means only first-party session data. (The most common example is to save items in a shopping cart in one session)

    If you save data persistent, or if you save third party cookies, I guess it always needs consent.

    In the new Google UMP consent SDK, you must give consent for:

    "Store and/or access information on a device"

    You can try to search other forums for similar questions:

    stackoverflow.com/questions/64587630/cookies-acceptance-policy-and-localstorage-and-sessionstorage

  • To encourage users to give consent (and show ads) and state that this is the only way for them to be able to play the game is more or less a so called "cookie wall". This is highly controversial.

    You can read this article

    termsfeed.com/blog/gdpr-no-cookie-consent-walls