- Android: Fix null pointer exception leading to app crashing after a second login (flow example: login -> graphApi -> logout -> login -> crash) (#568)
Breaking change: As of February 5, 2018, Facebook doesn't support anymore App Invites, therefore these methods have been removed.
This version introduce also a new optional variable for the Android installation.
-
iOS: App Invites support removed (#645)
-
Android: Add optional installation variable
ANDROID_SDK_VERSION(#550)(#646)
I did consider removing the methods for App Invites as a breaking change, even if these weren't already supported from Facebook since months.
I followed the semantic versioning idea the Ionic team recently published in their blog
@peterpeterparker
v1.10.1 Fix an issue regarding the versioning (v1.10 was missing in plugin.xml)
v1.10.0 introduces the last Facebook SDK for iOS
-
iOS: Update of the Facebook SDK v4.31.1 for iOS 11 (#631) (#634)
-
Android: Add a note in the README and Android Guide about the compatibility with cordova-android >= v7.0.0
The introduction of the new Facebook SDK for iOS 11 add a new confirm modal to the login flow.
This is the expected design flow defined by Apple which Facebook implemented. The cordova-plugin-facebook4 can't modify this behavior (as far as I know, @peterpeterparker).
On iOS 11.3, the user won't have the choice anymore between using the Facebook App or using Email/Phone number for Facebook login process but will go straight to the "Facebook - Accept permissions" screen.
Therefore, with this version, the user will still face only one modal during the login flow.
Because of the introduction of the new modal, the user might face two modals during the login flow. One asking him/her if he/she want to open Facebook and one again asking him/her as before if he/she want to open the Facebook App.
About the subject, you could for example have a look to this stackoverflow's post.
This is improved with iOS 11.3.