AnD4D's Forum Posts

  • Aww, was hoping this would make it in for the stable build. Oh well. I imagine with the new architecture it's a lot easier to update C3 than C2.

    Think I need to do a bit more research into C3's mobile exporter.

  • Just as an update, I think I finally got this cracked...

    I repositioned one of the plugins (cc.fovea.cordova.purchase) and got a new error code, telling me that the plugin "com.mcm.plugins.androidinappbilling" doesn't exist.

    I looked into it a bit more and read a few notes that purchase and inappbilling seemed to do the same thing... so I went ahead and removed it.

    I then updated the initial code to:

    <plugin name="cc.fovea.cordova.purchase" > <param name="BILLING_KEY" value="YOUR KEY GOES HERE"/> </plugin>[/code:23t3yhxk]

I uploaded it to Google and it all worked. Tested it out, and it looks like the code's working fine.

So @Ashley - I don't know if this might help you at all, and I honestly don't know if deleting that line of code will have any knock on effects elsewhere.

In any case, hope I help someone out there

  • I've been trying to get IAP working on Construct 2 and PhoneGap for about 3 weeks now, and it doesn't seem like anything I do gets me anyway.

    I heard that IAP works fine with a Construct 3 export, so I was hoping that someone could do me a favour.

    Could someone with Construct 3 make a brand new capx (or one already in use, doesn't matter), add the iap object into it, then export via Cordova and upload here a bit of text from the exported config.xml and hopefully the config.json?

    I know it's a big ask, and I have no idea if it'll help me at all. All I know is Construct 2 in combination with PhoneGap is currently broken, and there doesn't appear to be anyone who can or will fix it. Either that, or I'm missing something obvious.

    The error code I get is: "Error - One of your plugins requires a parameter: BILLING_KEY"

    and here are the plugins I'm using in my configs.

    <plugin name="cc.fovea.cordova.purchase" />
	<plugin name="com.mcm.plugins.androidinappbilling" />
	<plugin name="cordova-custom-config" />
	<plugin name="cordova-plugin-ad-admob" />
	<plugin name="cordova-plugin-file" />
	<plugin name="cordova-plugin-inappbrowser" />
	<plugin name="cordova-plugin-statusbar" />
	<plugin name="cordova-plugin-whitelist" />
	<plugin name="cordova-plugin-wkwebview-engine" />[/code:bb3kfxlu]

[code:bb3kfxlu]"plugins": [
		{ "id": "cc.fovea.cordova.purchase", "version": null },
		{ "id": "com.mcm.plugins.androidinappbilling", "version": null },
		{ "id": "cordova-custom-config", "version": null },
		{ "id": "cordova-plugin-ad-admob", "version": null },
		{ "id": "cordova-plugin-file", "version": null },
		{ "id": "cordova-plugin-inappbrowser", "version": null },
		{ "id": "cordova-plugin-statusbar", "version": null },
		{ "id": "cordova-plugin-whitelist", "version": null },
		{ "id": "cordova-plugin-wkwebview-engine", "version": null }[/code:bb3kfxlu]

Somewhere I appear to be missing a variable " <variable name="BILLING_KEY" value="YOUR_BILLING_KEY" />" which may very well slot into the purchase plugin at the top.

Like I said, a copy/paste of that code would be superb help. Hopefully...

  • Nepeo Will this be updated for Construct 2? I've not yet made the leap to Construct 3.

  • Nepeo - Thanks for your post. I did, however, change this version number during my export for PhoneGap and it never worked.

    I ended up opening the file up in Android Studio, and while it showed 1.0.0.1, the version code remained 10000. However, that is shown in your table. Therefore, should I have used 1.0.1.0?

    I didn't see that documented anywhere, and did search all over this site and a few others. Is the quote you posted from a manual or tutorial?

    Is this likely to be added to the export for simplicity? As you said, to avoid that small confusion?

    My current build is 0.1.0.1 because I consider it in alpha, but my version code is 10001.

    Thanks again for your reply.

  • NN81 Jesus, why are you stalking me around the forum? You don't know what you're talking about and Ashley asked me to post this bug. The point of Construct is no coding. ATM, you need to do coding. Go find another project, please.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Not meaning to be rude, but so far I've spent 2 days explaining something to you and had to go over the same stuff way too many times before you understood. Ashley has said that if we have to go into code to get stuff to work, there's something not right.

  • This is boring. Why are you getting involved if it's tastes? You're happy, I'm not. Let's move on.

  • NN81 - Never heard of CLI before. Just had a quick look online, and it looks like you need to do some coding here and there. With PhoneGap, you literally just zip your export and upload it. I would have thought PhoneGap would be capable of updating the version code, but I guess not. I can access the AndroidMenifest.xml using Android Studio to open up the APK, but that's a step I don't deem necessary. It takes seconds to open the config file and add in the line, but it'd be nice if it weren't a step at all.

    My method doesn't require anything but Construct and PhoneGap's auto-sign and build site. It's so much simpler.

    Just had a read of your tutorial, and I still think PhoneGap is easier, excluding the VersionCode, which I'm hoping Scirra can do something about during export. With PhoneGap, I can build Android, iOS and Windows apps all with pretty much a single click.

    For me, fewer steps FTW.

  • NN81 - Before building the APK. Construct doesn't export the APK. I need to then run it through PhoneGap so it'll build the signed APK, then upload that to Google... at which point it demands an updated VersionCode.

  • NN81 - What you're referring to is the release version.

    Taken from my Google Play Console in the Alpha release atm...

    Release: 0.1.0.0 (This is changed by the #.#.#.# code)

    Today, 15:10: Full roll-out

    Supported devices: 5907

    Unsupported devices: 8741

    Excluded devices: 0

    Manage devices

    1 APK version code: 10002 (This is changed by the VersionCode... which is what Google requires.)

  • Problem Description

    The exported XML file when using Cordova doesn't include a VersionCode. It'd be nice if this was included within Construct, or even the export section.

    Attach a Capx

    https://1drv.ms/u/s!Am3CPIM7woZ9zh5jsEb-ZZ5XL_zL

    Description of Capx

    But you can literally use any CAPX with an ID and description. This is just a blank capx (with included properties) because rules...

    Steps to Reproduce Bug

    • Open CAPX
    • Export using Cordova
    • Open exported config.xml
    • Note that there's no line regarding the android-versionCode

    Observed Result

    When you upload an APK to Google Play Store, you see a version code. It defaults to 10000. If you then try to upload another APK, Google will throw up an error telling you that you have to upload an APK with a different version code. Note that the version code is different to the version that is included in Construct's Properties section.

    Expected Result

    Within the config.xml file, you're meant to be able to change the version code.

    I added it in the top line, highlighted below in bold.

    version="1.0.0.0" android-versionCode="10001" xmlns="http://www.w3.org/ns/widgets"

    When I add this line in, build an APK and upload it to the store, it's accepted and works. Surely we should be able to edit this within Construct, rather than opening it up after each and every export, adding this line and then going through the normal process. At the very least, this line should be included in the exported XML already. I do note that if I change the "Version" number within Construct, the XML is changed already.

    Again, I emphasise that Version is not the same as VersionCode.

    Affected Browsers

    N/A

    Operating System and Service Pack

    Windows 10

    Construct 2 Version ID

    r249

  • NN81 - The "version" in properties is different from the version code Google Play requires. You can upload one APK without issue, but the second APK requires a different Version code... as does the next one, and the next one. Editing it each and every time is a little bit annoying, as I need to keep note of the version number each time. Fine for normal games, but annoying for those with many free updates or bug fixes.

  • Ashley - This is a bug??? Also, I'm afraid I don't know who — / Iain is. Bug reports typically require a capx to be created and shared, but one could simply export a blank project and see the feature I'm requesting. I only see reference of shortercode on the Construct 3 Github site, while I'm talking about Construct 2.

  • Hi Ashley,

    Quick request

    I've been trying to figure out a way to update my APK on the Google Play Console, but each time it requested I upload an APK with a different Version Code.

    Took me ages to figure out what I needed to do. Trying multiple programs... with no luck.

    In the end, I simply opened the config.xml file and added in this line (in bold) between the other two:

    version="1.0.0.1" android-versionCode="10001" xmlns="http://www.w3.org/ns/widgets"

    Took quite a bit of research to find out that I could add this in, as it's described as optional. Not sure why it isn't included by default.

    My question is, is there a reason why this isn't included when we build the app? Also, is it possible to perhaps make this process a bit easier? Say including a Version Code properties section within Construct itself? Perhaps next to the Version number in the about section?