[Kool]

Hi Team,

I’ve tried out the various demos with Facebook plugin integration, such as GameNetworkTest, plug-in demo in example launcher, etc.

Nothing seems to happen when I click the Facebook-related buttons.

Is there something I’m missing?

[AlexFelgo Team]

Hi Kool,

we’ll have a look at this tomorrow and get back to you.

Cheers,
Alex

[Lorenz]

Hi Kool,

In the Sample Launcher, it’s obvious that the buttons don’t work, because the Facebook Plugin only supports mobile devices.

Did you try deploying one of our examples to your Android or iOS device, or did you try the PluginDemo project?

Cheers,

Lorenz

[Kool]

Hi Lorenz,

I did try deploying to an android device but had the same result. I’ll have a go with the PluginDemo.

Many thanks.

[Kool]

I’ve tried out Squaby on Android and when clicking ‘Connect with Facebook’ in the network view nothing happens. I do get the following in the console:

 

D/Squaby Dev( 4870): qrc:///qml/VPlay/gamenetwork/gnView/GnViewButton.qml:39 (onPressed): qml: button pressed: Connect with Facebook
D/Squaby Dev( 4870): qrc:///qml/VPlay/gamenetwork/gnView/ProfileView.qml:278 (onClicked): qml: ProfileView: fb-button clicked with text: Connect with Facebook

 

I’ve also tried launching various other projects and get the same result, sometimes without the above in the console.

 

I couldn’t find the PluginDemo in the example source directory.
Any clues on how to proceed from here?

[Marcin]

Hi Kool,
I did quick test for pluging demo and I can get the Facebook log in page(on Android device, after deploying).
So the plugindemo is here: https://github.com/Felgo/PluginDemo
Clone it from Github, open PluginDemo.pro in QtCreator.

Even with the free license it comes with, and the watermark, you should be able to run the example.

[Kool]

Hi All,

Many thanks for your feedback. I’ve cloned the GitHub repo and deployed it to my Android device but still get the same issue: I can see the ‘Login’ button, but upon clicking it nothing happens.

 

I uninstalled the deployed version and installed the App Store version on the GitHub page: https://play.google.com/store/apps/details?id=net.vplay.demos.PluginDemo

 

This works and I can successfully login and it reads my Facebook profile data. The version on the App Store was last updated over a year ago.

 

Is there anything I can provide the dev team to help diagnose this issue?

[GüntherFelgo Team]

Hi Kool!

Do you see any lines related to Facebook in the Application or Compile Output?

Please also make sure that your build.gradle correctly links the Facebook framework in the dependencies section with the line

 dependencies {
   compile 'net.vplay.plugins:plugin-facebook:2.+'
 }

In order to correctly link and build the project with the configured plugin frameworks, please also see if “Use Gradle” is activated for the Android Build Kit in the “Projects” tab on the left side of Qt Creator.

You can also configure Gradle as default build system for Android in the Qt Creator Options:
Devices – Android – “Use Gradle Instead of Ant”

Let me know if this helps!

 

Note: After activating Gradle, please make sure to remove any previous installations on your device, as well as the build folder on your file system to make sure you get a fresh and clean build with Gradle.

 

Best,
Günther

 

 

 

 

 

[Kool]

Hi Gunther,

I’ve followed the Felgo documentation on deploying to Android and made the changes you suggested above to use Gradle instead of Ant, but now have the following issue when deploying to my device:

A problem occurred evaluating root project 'android-build'.
> Failed to apply plugin [id 'com.android.application']
   > Gradle version 2.10 is required. Current version is 2.2.1. If using the gradle wrapper, try editing the distributionUrl in C:\Users\fayza\Documents\workspace\build-PluginDemo-Android_for_armeabi_v7a_GCC_4_9_Qt_5_8_0_e60c1b-Debug\android-build\gradle\wrapper\gradle-wrapper.properties to gradle-2.10-all.zip

 

Could it be related to the Android SDK suggested in the Felgo documentation?

 

Many thanks

[Marcin]

Hi Kool,
This is unfortunately a common issue sometimes when using examples preprepared earlier on a different machine.
It is a one time fix.
Please follow what the error tells you.
Edit file:

C:\Users\fayza\Documents\workspace\build-PluginDemo-Android_for_armeabi_v7a_GCC_4_9_Qt_5_8_0_e60c1b-Debug\
android-build\gradle\wrapper\gradle-wrapper.properties

Change the last line, distrbutionUrl variable probably, make sure that it ends with gradle-2.10-all.zip not 2.2.1, what is probably there. Try again.
Why this happens? Need some explanation from Felgo team.
`

[GüntherFelgo Team]

The gradle-wrapper configuration is usually automatically created by Qt Creator during the Android Build. The default version which is used there is 2.2.1 – but some framework dependencies require 2.10 to be used.

 

[Kool]

Hi Marcin and Gunther,

Thank you for your responses.

Gunther, does this mean for each new project, one must manually change the gradle-wrapper.properties file as Marcin suggested?

Many thanks!

[GüntherFelgo Team]

That is required at the moment when this issue occurs. We will have a look if we can improve our wizards / demos to automatically use this version if necessary.

 

[Kool]

Hi Marcin, Gunther,
Many thanks for your input. With your suggestions I can deploy the PluginDemo and use the Facebook plugin.

 

I do have some feedback on the installation procedure:

1. On the deploy to Android page: https://felgo.com/doc/vplay-deployment/#android-sdk-tools – Under section ‘Configure Qt Creator’, alongside the textual description of setting paths for JDK, Android NDK, etc – it should also explicitly state ‘Check use Gradle instead of Ant’ – I missed this step because it wasn’t in the textual instructions
2. Include Marcin’s suggestion for change the gradle.properties wrapper if required

 

Thanks again for your help guys!

 

[Marcin]

Hi all,
I agree with Kool, there is some space for improvements in terms of documentation.
In the end it can be frustrating that with limited time you have, as an indie developer(most of the time), you are force to spend more than needed on technical issues.
Anything that can save time in this regard is a welcome change.