Suikama's Recent Forum Activity

  • Ah, I have not signed up for CocoonJS Extensions so I don't have access to that page.

    I'll try signing up for Premium and see if it works.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • So I created a game, compiled an .apk file with CocoonJS, signed and zipaligned the apk, and put it on the Google Play Store. However I've now run into an issue with trying to get In-App purchases to work.

    In the Google Play Developer Console is states the following in the In-app Products tab for my game:

    "Your app doesn't have any in-app products yet.

    To add in-app products, you need to add the BILLING permission to your APK."

    What I have attempted to do is I opened the original .apk file, added the "IInAppBillingService.aidl" file, and modified the code in "AndroidManifest.xml" by adding the line:

    <uses-permission android:name="com.android.vending.BILLING" />

    Then I resigned/zipaligned the whole thing and tried adding it to Google Play, but Google returned the following error:

    "Your APK cannot be analyzed using 'aapt dump badging'. Error output:

    Failed to run aapt dump badging:

    W/ResourceType(11858): Bad XML block: header size 28257 or total size 1936025193 is larger than data size 339

    ERROR: AndroidManifest.xml is corrupt"

    Has anyone else had any success publishing a game using Construct 2 and CocoonJS with working In-App Purchases and can tell me what I'm missing or did wrong? Thanks.

  • Here's a possible solution for those having flickering problems, namely one that occurs whenever the game changes layout:

    CocoonJS does not support letterbox scaling and if you try it, CocoonJS will default to Scale outer for fullscreen. If you use Scale outer with Construct 2 however, and you do not use the Scroll to behaviour anywhere in your project, then every time the game moves from one layout to another, Construct2 first puts everything in the middle of the screen for the first frame(s), then moves it all to the left side, resulting in a jarring flicker.

    The way to fix this is simply add a Scroll to (0,0) call to the start of each layout.

Suikama's avatar

Suikama

Member since 6 Dec, 2012

None one is following Suikama yet!

Connect with Suikama

Trophy Case

  • 11-Year Club
  • RTFM Read the fabulous manual
  • Email Verified

Progress

13/44
How to earn trophies