Learn what Felgo offers to help your business succeed. Start your free evaluation today! Felgo for Your Business


OverviewFelgo 3 Support (Qt 5) › Question Facebook plugin updates

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


    Hi Team,

    Is VPlay Facebook ready for the Facebook Graph 2.4 API? There’s some pretty stark warnings on the developer website and also seems like some features are being deprecated: Reminder: Graph API v2.3 will be deprecated on July 10, 2017.

    I wouldn’t want to spend a week working on integrating it for it to break down.


    As a side note… Thought I’d mention the latest VPlay PluginDemo needs updating: (onOpenSessionFailed): qml: Open session failed Invalid key hash. The key hash QKwhWqDqW6SYqMx6mJ5Q/9vhIdM= does not match any stored key hashes. Configure your app key hashes at https://developers.facebook.com/apps/1014223965320966/
    I managed to get it up again by registering my own app ID on Facebook with a new Android hash.


    Many thanks,


    Felgo Team


    The Facebook Plugin is implemented with the Facebook Framework 4.17.0 for iOS and Android, which use Graph API 2.8. You can see which Facebook Framework version the plugin uses at the moment in the Facebook Plugin documentation.
    Regarding the key hash:

    Each Android build has it’s own key hash, so when you build the Plugin Demo for Android yourself, it is not possible for us to have this key hash included in the configured hashes for the Felgo PluginDemo Facebook app.

    This is why we also have the Plugin Demo published in the stores, which allows users to install and test it with the store version that uses a valid hash.





    So the hashes are project-specific and for each new project a hash must be generated.

    Thanks Gunther!


    Felgo Team

    To be more exact, the hash actually comes from the Android APK signing process. If you do not explicitly sign your Android APK, a new hash is created when building, which will be different for every project and every device that you build the project from.

    When you explicitly sign your APK for release with a keystore, the hash for the app will be the same regardless of the device you build it on. So when releasing the app, you should make sure to explicitly sign the APK and use this hash as the main hash for your Facebook app.


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

RSS feed for this thread

You must be logged in to reply to this topic.

Qt_Technology_Partner_RGB_475 Qt_Service_Partner_RGB_475_padded