Not sure as to why Construct 2 IAP didn't work. I believe it was something on Google Play side of the house, maybe an update that was not incorporate d into C2, but in C3 that issue was fixed.

Ashley - Is this correct? I've been trying to get IAP working on Construct 2 with PhoneGap for about a week now. Is the solution to upgrade to Construct 3? When I try to upload any app with the IAP plugin included to PhoneGap, I get an error saying:

"Error - One of your plugins requires a parameter: BILLING_KEY - You can fix this here"

According to the OP, they just did the exact same thing on Construct 3 and it worked without them seemingly needing to jump through hoops.

*EDIT - I should add, the "You can fix it here" just takes you to the plugin section... which either creates a malformed config file or doesn't fix the Billing Key issue.

NN81 Do you know how or where I'm meant to implement that? As far as I can see, it's just a bunch of code without any instructions of where I need to put it. Sorry for the hassle.

What I ended up doing was adding the browser plugin to my game and giving the back button a function. This meant when a player pressed it, it didn't close the program.

orangpelupa Did you ever get this sorted? Did gumshoe's links help you, because they mean nothing to me.

Anyone know how to get this working?

I've looked at some tutorials, but they all appear to be outdated now, mainly referring to the Intel XDK which is no longer being maintained.

When I export my app and upload it to PhoneGap, I get an error message for my android upload telling me I'm missing a "BILLING_KEY". Now some tutorials tell me that I get my billing key after I upload my app, which is odd seeing as I can't even get a build I can use.

Another thread I found had the same issue, but they said "Oh, I switched over to C3 and it works now!". What about those of us that are still using Construct 2?

Other people have sent me to sites such as GITHUB, where all I see is a wall of text with no explanation as to what I'm meant to do with it. One recently was in Italian, which just confused me even more.

I can build the app with no issues so long as I don't use the IAP plugin, but as soon as I add that I get errors.

Am I to assume that Construct 2's IAP plugin is just broken, seeing as it apparently works without issue in Construct 3?

Nope, didn't have to follow that link. Just updated IAP from Construct 2 to Mobile IAP in Construct 3 and Google Play store accepted the apk. In app purchases was unlocked afterwards in Google Play Console.

Sorry for bringing this back up, but I'm experiencing the same issue now. Are you saying Construct 2's IAP is buggy and that we need to use Construct 3 to do this now?

Does anyone know how to disable the back button on an Android mobile game?

In the past, when I pressed it a message popped up asking me if I wanted to close the app. I believe this was with CocoonJS, however I'm now using Cordova.

Now, when I press it, the game instantly closes without any notifications. I'm building a game that requires the player pass the phone to another player, and on occasion, with my phone (Samsung Note) a player can press the back button by mistake. If they press any other button, including the power button, the game remains open. The back button, however, as I said, closes it, and when you open it again, it starts from the beginning.

Any ideas?

Ashley I didn't see it as a bug, just a missing feature. As I said, I've not really looked into mobile development really until recently.

I've just done my own keyboard, but it's not ideal because if players make an error they have to delete all the characters after the error to fix it, rather than just edit the text.

It's not a big deal, really, but it's not great.

>

> > Seriously, I'd make my own keyboard out of sprite frames.

> >

> Hey Newt! Yeah, I've thought about that, but I'm also looking at allowing names to be entered, which would require all the letters added. Seems like a lot of effort just to enter names JUST because the enter key and focus don't work.

>

> I was hoping that I was missing something basic... rather than Construct missing something basic.

>

I've spent a lot of time battling this, and usually do either one of two things:

1. Design my own keyboard.

2. Make sure all HTML textfields are in the top half of the screen.

The problem is that with Construct's screen scaling, browser manufacturers are too inconsistent to make sure things are always done the same way. The only surefire way to avoid these issues is to build your own keyboard.

cjbruce Yeah... keeps coming back to that, but the fact that it appears to be a requirement is absurd. I originally used the "Scale Inner" scale, but when I put the texbox at the top, it vanished, and recentred my screen, no mater my scroll to point. In the end, I had to use "Scale Outer", which results in a teeny tiny layout when the keyboard appears. It's as though it zooms out.

It's annoying, looks stupid is and unprofessional, but it works.

I'm also aware that with my app exported with Cordova and built with PhoneGap, whenever I touch a textbox, the toolbar/status bar at the top of mine and 2 other phones I've tested it on appears it will never go away again. So if I touch the textbox, I can't get rid of the little clock. Even though I check the box at export.

So that's 3 bugs with mobile development in relation to the textbox.

1) The return button does nothing

2) The soft keyboard vanishes if the keyboard overlaps it or if it goes off screen (often caused by scaling)

3) The status bar appears and won't go away

Ashley - Are you aware of any of these issues? Or do you not consider them issues?

When the best answer is "Make your own keyboard", I struggle to believe that there's not a problem here. Are these things fixed in Construct 3?

Seriously, I'd make my own keyboard out of sprite frames.

Hey Newt! Yeah, I've thought about that, but I'm also looking at allowing names to be entered, which would require all the letters added. Seems like a lot of effort just to enter names JUST because the enter key and focus don't work.

I was hoping that I was missing something basic... rather than Construct missing something basic.

After using C2 for many many years, my wife asked me to develop a mobile app for her work. It involved entering some numbers into a textbox and it would do some calculations.

The thing is, it's not acting how I expected.

If the textbox ever goes off screen or gets covered up by the keyboard, the keyboard is immediately pulled down. This was caused by the scale not being perfect on the mobile device, so it would scale the screen appropriately. I had the textbox at the top, so it would sometimes disappear.

However, I've seen a few examples where the textbox could be placed at the bottom, and if the keyboard was summoned it would slide the textbox up... but in my experience (and this thread I found: https://www.scirra.com/forum/problem-with-textbox-and-mobile-keyboard_t185196), the keyboard just overlaps the textbox and, as I said, that causes it to close the keyboard as the textbox is no longer in focus. Strangely, in the linked experience, their keyboard remains, but they can't see what they're typing.

In addition to this, I can't press the enter button on the soft keyboard to confirm that I'm done entering details. Why is that exactly? The enter button does nothing at all. People have to press the back button or onto the layout in order to close the keyboard.

Is it possible to have events for the software keyboard?

Construct 2 has typically been promoted as being great for mobile development since my time here, and finally when I do decide to make use of that functionality, it's missing what I consider pretty basic functions? Colour me very surprised.

Well this sucks...

Seeing this as well. Just in the process of downgrading to VS2015 to see if that helps.