Forums

OverviewV-Play 2 Support (Qt 5) › Flurry crashes on Android device

Tagged: 

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #14886

    Caeser

    Hi,

    Adding Flurry to my Main.qml seems to crash the game.

    I tried setting the stage property to publish but its the same.

    it only happens when I integrate Flurry into my qml file

    Error is below

     

    I OpenGLRenderer: Initialized EGL, version 1.4

    W libColorGame.so: (null):0 ((null)): NOTE: you are running a development build in Release Mode. However, the Release mode is recommended only for publish builds that are released to the app stores and for final testing. You can enable a publish build in the config.json file in your qml folder by setting the “stage” property to “publish”. For more information see: http://v-play.net/doc/vplay-publishing/

    W linker : /data/data/com.drinkapps.WhiteisBlack/qt-reserved-files/qml/QtQuick.2/libqtquick2plugin.so: is missing DT_SONAME will use basename as a replacement: “libqtquick2plugin.so”

    W linker : /data/data/com.drinkapps.WhiteisBlack/qt-reserved-files/qml/QtQuick/Window.2/libwindowplugin.so: is missing DT_SONAME will use basename as a replacement: “libwindowplugin.so”

    W linker : /data/data/com.drinkapps.WhiteisBlack/qt-reserved-files/qml/QtQuick/LocalStorage/libqmllocalstorageplugin.so: is missing DT_SONAME will use basename as a replacement: “libqmllocalstorageplugin.so”

    W linker : /data/data/com.drinkapps.WhiteisBlack/qt-reserved-files/qml/QtQuick/Controls/libqtquickcontrolsplugin.so: is missing DT_SONAME will use basename as a replacement: “libqtquickcontrolsplugin.so”

    W linker : /data/data/com.drinkapps.WhiteisBlack/qt-reserved-files/qml/QtQuick/Particles.2/libparticlesplugin.so: is missing DT_SONAME will use basename as a replacement: “libparticlesplugin.so”

    W linker : /data/data/com.drinkapps.WhiteisBlack/qt-reserved-files/qml/QtGraphicalEffects/private/libqtgraphicaleffectsprivate.so: is missing DT_SONAME will use basename as a replacement: “libqtgraphicaleffectsprivate.so”

    W linker : /data/data/com.drinkapps.WhiteisBlack/qt-reserved-files/qml/QtMultimedia/libdeclarative_multimedia.so: is missing DT_SONAME will use basename as a replacement: “libdeclarative_multimedia.so”

    W linker : /data/data/com.drinkapps.WhiteisBlack/qt-reserved-files/qml/QtQuick/Layouts/libqquicklayoutsplugin.so: is missing DT_SONAME will use basename as a replacement: “libqquicklayoutsplugin.so”

    W Colorfool: (null):0 ((null)): QQmlApplicationEngine failed to load component

    W Colorfool: (null):0 ((null)): assets:/qml/Main.qml:30 Cannot assign to non-existent property “onComplete”

    09-16 02:46:56.591 1036 1508 W Colorfool:

    F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x4 in tid 1508 (QtThread)

     

    My Gradle file 

     

     

    buildscript {
        repositories {
            jcenter()
        }
    
        dependencies {
            classpath 'com.android.tools.build:gradle:1.1.0'
        }
    }
    
    allprojects {
        repositories {
            jcenter()
            maven { url 'https://sdk.v-play.net/maven/' }
        }
    }
    
    apply plugin: 'com.android.application'
    
    dependencies {
        compile fileTree(dir: 'libs', include: ['*.jar'])
        // Add Play Services & support library
        compile 'com.google.android.gms:play-services:7.5.0'
        compile 'com.android.support:support-v4:22.0.0'
    
        // Add Flurry
        compile 'net.vplay.plugins:plugin-flurry:2.+'
    }
    
    android {
        /*******************************************************
         * The following variables:
         * - androidBuildToolsVersion,
         * - androidCompileSdkVersion
         * - qt5AndroidDir - holds the path to qt android files
         *                   needed to build any Qt application
         *                   on Android.
         *
         * are defined in gradle.properties file. This file is
         * updated by QtCreator and androiddeployqt tools.
         * Changing them manually might break the compilation!
         *******************************************************/
    
        compileSdkVersion androidCompileSdkVersion.toInteger()
    
        buildToolsVersion androidBuildToolsVersion
    
        sourceSets {
            main {
                manifest.srcFile 'AndroidManifest.xml'
                java.srcDirs = [qt5AndroidDir + '/src', 'src', 'java']
                aidl.srcDirs = [qt5AndroidDir + '/src', 'src', 'aidl']
                res.srcDirs = [qt5AndroidDir + '/res', 'res']
                resources.srcDirs = ['src']
                renderscript.srcDirs = ['src']
                assets.srcDirs = ['assets']
                jniLibs.srcDirs = ['libs']
           }
        }
    
        lintOptions {
            abortOnError false
        }
    }
    
    
    
    

     

    #14892

    Günther
    V-Play Team

    Hi Caesar,

    the build.gradle looks correct. but there is an error mentioned in the Log Output:

    W Colorfool: (null):0 ((null)): assets:/qml/Main.qml:30 Cannot assign to non-existent property “onComplete”

    -> The signal to run code when the component is complete is called “Component.onCompleted“, so using the unknown “onComplete” name causes the crash.

    Best,
    Günther

    #14896

    Caeser

    Hi Gunther,

    That seems to fix the error. I copied the snippet straight from the V-Play website and it shows.

    http://v-play.net/doc/plugin-flurry/.

     

    So I have to wait 24 hours to confirm if my Game is sending the events?

    import VPlayPlugins 1.0
    
     Flurry {
       id: flurry
    
       // From Flurry Dashboard
       apiKey: "<flurry-api-key>"
    
       Component.onComplete: {
         flurry.logEvent("App started");
       }
     }
    #14897

    Günther
    V-Play Team

    Thanks for pointing that out, we will fix that error in our documentation! 😉

    If you have set up your flurry account and use the correct API key, the events should show up after some time. And yes, it might take a while before they do, but it can also be shorter than 24 hours (I think the new Flurry Dashboard is faster with processing and showing events).

    If no events show up after a short time, it is just too soon to decide that something is going wrong, so we recommend to wait at least 24 hours.

    Best,
    Günther

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

RSS feed for this thread

You must be logged in to reply to this topic.

Voted #1 for:

  • Easiest to learn
  • Most time saving
  • Best support

Develop Cross-Platform Apps and Games 50% Faster!

  • Voted the best supported, most time-saving and easiest to learn cross-platform development tool
  • Based on the Qt framework, with native performance and appearance on all platforms including iOS and Android
  • Offers a variety of plugins to monetize, analyze and engage users
FREE!
create apps
create games
cross platform
native performance
3rd party services
game network
multiplayer
level editor
easiest to learn
biggest time saving
best support