Find the Best Demos and Examples

Check out this quick tour to find the best demos and examples for you, and to see how the Felgo SDK can help you to develop your next app or game!

Forums

OverviewFelgo 2 Support (Qt 5) › Troubles with license key

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #8774

    Heini

    Hi,

    I have serveral problems with the license key. I generated one for my game.

    1) As my games versionCode is 6 (like stated in the config.json), i also generated the licensekey with versioncode 6. This works on Windows, but when I deploy the game to iOS, i get the following debug-output:

    “ERROR: license: runtime versionCode: “1” , license versionCode: “6””

    So on iOs I have always to use a licenseKey with versioncode 1.

    2) Even if I run the app on publishmode (config.json) and compile it as Release, the small textline (license reminder) on the bottom left corner won´t dissapear!!! This is on all platforms I tested!

     

    Cheers,

    Heini

    #8775

    Christian
    Felgo Team

    Hi Heini,

    can you please send your project (or an extracted test case) to support@felgo.com?

    Cheers, Chris

    #8776

    Christian
    Felgo Team

    It sounds like the config.json is not deployed correctly in your case. Can you test, that in the shadow build folder on Windows, the config.json file is the same as you set in your project?

    Cheers, Chris

    #8791

    Heini

    Hi,

    now I realized a parsing problem with the json file on iOS. I checked the file several times, but was not able to localize the error. Maybe its because i modified it with the standart Mac OSX texteditor who probably saves also its own stuff in the file. However, after replacing the json file with the one from the PC, the license reminder is not showing any more.

     

    Thanks,

    Heini

    #8793

    Christian
    Felgo Team

    Hi Heini,

    thanks for sharing!

    Cheers, Chris

Viewing 5 posts - 1 through 5 (of 5 total)

RSS feed for this thread

You must be logged in to reply to this topic.