Bootfit's Forum Posts

  • I have a couple of simple apps on the Play & App Store that I want to put onto Facebook Instant Games.

    First off, as the apps have Google Admob plugins, plus functionality to add scores to Google leaderboards and share scores via social media. Will I need to remove these features or are they compatible as they are with the Facebook Instant Games? If not, I’m guessing I’ll have to create a duplicate app with these features removed and upload that.

    If the Admob plugins aren’t compatible is there a similar feature you can add on instant games?

    Lastly, can anyone give me some pointers on where to start, outside of the documentation available here?

    Cheers all :)

  • Yeah, except we've already made our amends in r204 and saved etc and when we tried to export/build that's when we discovered the Keystore/password issue. Then when we try to open these projects again in r197 we get the following error message:

    This project cannot be opened since it was saved in a newer version of Construct 3. The project was saved in r204, and you are currently using r198. Use a newer version of Construct 3 to open the project.

    So yeah, until the patch comes we're screwed.

  • Good. Because the issue I'm now having from having to create and sign with a new Keystore is when updating the app on the Google Play Store I'm getting the following error:

    Upload failed

    You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):

    [ SHA1: ORIGINAL FINGERPRINT HERE ]

    and the certificate(s) used to sign the APK you uploaded have fingerprint(s):

    [ SHA1: NEW FINGERPRINT HERE ]

    So once this new update to revert to the original system is live I'll be able to use my original keystores for updating my existing apps.

    Until the update is live though, we're all screwed.

  • Ashley

    Has there been any movement on this? Is it worth making an announcement to the whole customer base?

    Those with apps made live before the changes were implemented will no longer be able to update them using this new signing system, and anyone who has made a new app using the new signing system may not be able to update their apps if the new system is reverted to the old system.

    Therefore currently working in Construct is pointless as we don't know if we'll be able to update/amend any app we're working on once they're live - as we don't know which system will be in place.

    I think you need to make the customers aware of this ASAP.

  • The problem we have is the build tool was (it seems) updated to ignore the key password when creating keystores. So people kept entering a key password when creating a keystore, which was ignored, then re-entered it when signing the app, and then getting "wrong password" errors. This change was in the beta release for about a month before it came to a stable release, which gave the impression the change was OK.

    So educate people who were having the initial problem - everybody who had to build previous to this had to learn.

    If we add back a key password field just for signing, we'll be asking people to enter a password they never previously specified, which would probably cause further confusion.

    If this new system has only be implemented for a month there will be so many less apps that will have be affected, as opposed to all the apps that have been using a password key since the first days of using Construct.

    So it's not clear to me what to do here, it seems this change to the build tool has thrown a spanner in the works.

    Do some proper testing at your end and try it out on some of your own apps?

  • When I was learning how to build my first app with Construct I learnt that I’d you lose your keystore then you couldn’t paste your app once live - so don’t lose your keystore a otherwise you’re screwed.

    Seems odd that Scirra wouldn’t know this And would create an update that blocks any current live from ever being updated.

  • Sounds to me like you’ve fixed one problem to create another that will affect the whole community.

  • Yeah I thought you always had to use the same keystore otherwise you can’t update your live game.

  • I've just updated to the latest stable release (r204) and I'm trying to export for Android.

    I do the usual Menu > Project > Export > Android (Cordova) > Choose Signed Release APK...

    Then further down the interface I get to choose My Keystore and input Keystore Alias, Keystore Password but there's no box to input Keystore Key and so the build fails...

    Am I missing something? Is this a new feature of r204 that I need to check/uncheck something previously down the line or is it an error?

  • Is there an issue with or a time delay on the Construct Reddit forums?

    I've just posted a question asking how to log in to the Google Leaderboards and it's not appearing on the Construct Reddit timeline.

  • Bump!

    Folks, any feedback on what I'm getting wrong with trying to post to the Google Leaderboards?

  • I'm looking at putting my latest game up on Facebook using the Instant Games plugin. When going about this, would you recommend creating a whole new app (or duplicating the existing app) with Facebook-specific events, or simply adding specific Facebook-specific events to the exiting app?

    Has anyone had experience with this?

    cheers all :)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Folks - any advice on what the issue may be here?

  • I have a countdown timer before my game starts... 3...2...1...GO!

    The countdown are sprites rather than text. I want them to start at 100% size and increase to 200% size while fading out over 0.8 seconds.

    I've got the fade action sorted, but how do I animate the increase in size?

    cheers all :)

  • I’m having trouble with some users being able to upload their scores to the Google Leaderboards.

    Here’s the relevant portion of the event sheet:

    As you can see the events run as follows:

    1. User presses the yellow leaderboard button

    2. Google Play > Sign in

    3. Google Play > On signed in > submit score to leaderboard

    4. Google Play > On signed in fail > call an error function (this brings up a popup telling the user how to log in to Google Play)

    5. Google Play > On score submit success > show leaderboard

    6. Google Play > On score submit fail > call general error function (another popup)

    I’ve been told by several people that when they press the leaderboard button nothing happens. No Google Play Sign in or no error pop up either. And yet I’ve had other people who are able to post their scores to the leaderboards with no problem.

    So can anyone spot what the issue is here?

    I notice there’s an event that goes Google Play > Is signed in - how does this differ from point 3 above On signed in?

    Can anyone post a screenshot of their process for successfully signing in and submitting to the Google Leaderboards?

    Cheers :)