Twitter WKWebView alternative AND breaking issues (for iOS)

[rolinger]

It doesn't appear that the @chroa branch is maintained anymore, but @tien271 created a specific fork to be compatible with iOS WKWebView requirements now. cordova-plugin-twitter-connect-wkwebview - however, that plugin ONLY works if you already have a fabric account (you can't create new ones anymore) and who knows for how long it will continue to work - I suspect that will even break soon.

What are the alternatives to the Fabric key...should this be a Firebase crashlytics plugin by now? Fabric has been dead for a while.

[Merwan1010]

You can make the plugin cordova-plugin-twitter-connect-wkwebview work using Firebase.
Just after creating a new project, you will see a firebaseConfig object. Use the field apiKey as a fabric API Key and it should work smoothly.

[rolinger]

ah, ok...thanks for the update. Someone should really update the documentation on this plugin and/or properly maintain it. Its too popular of a plugin/resource to not be kept up or maintained.

[rolinger]

@MadyAkira

BREAKING ISSUE: The recommended cordova-plugin-twitter-connect-webview DOES in fact work and allows your app to get approved by the Apple app store (twitter-connect-plugin has UIWebView references that will cause your app to get rejected) - works great. But...a big BBUUTT...the newer plugin causes deeplinks window.handleOpenURL to break. The twitter plugin has its own version that overrides the customurlscheme one and will prevent you from passing url paramters when you open your app with a deeplink custom scheme.

I don't have time right now, but I am going to test some stuff later...load twitter first, customurlscheme second - and see if that resolves the problem. As of now I can say customerurlscheme first and twitter-connect-webview second def breaks parsing external parameters.

It took me the last 24+ hours to figure out it was this new twitter plugin that was breaking my deeplink url parameter parser.

[Merwan1010]

Did your app got accepted by the playstore also ?

[rolinger]

@MadyAkira - I still have the standard twitter-connect-plugin in my android version because Android doesn't use WkWebview nor does Android have the UIWebView restrictions that Apple has.

But with Apple, the forked plugin cordova-plugin-twitter-connect-webview did allow my app to be accepted by Apple - but I then discovered the plugin was interfering with customurlschemes ability to managing inbound deeplink parameters using window.handleOpenUrl() - so I had to remove the plugin altogether and will most likely need to create another fork of the plugin to figure out how to use the twitter plugin without interferring with the customurlschemes plugin.

[Merwan1010]

@rolinger I used the webview plugin for Android too, and since my app got rejected by the Playstore with this reason :

We don’t allow apps whose primary purpose is to provide a webview of a website(...)

I will uninstall it and use the 'normal' version instead.

For the deeplink problem that really suck... i hope you'll quickly find a solution.

[rolinger]

You should reach out to Android about that, it's just a Twitter plugin that is compatible with webview, it doesn't mean what they are implying it is. Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: MadyAkira <notifications@github.com> Sent: Monday, November 2, 2020 7:43:59 PM To: chroa/twitter-connect-plugin <twitter-connect-plugin@noreply.github.com> Cc: rolinger <rolinger1@hotmail.com>; Mention <mention@noreply.github.com> Subject: Re: [chroa/twitter-connect-plugin] Twitter WKWebView alternative AND breaking issues (for iOS) (#30) @rolinger<https://github.com/rolinger> I used the webview plugin for Android too, and since my app got rejected by the Playstore with this reason : We don’t allow apps whose primary purpose is to provide a webview of a website(...) I will uninstall it and use the 'normal' version instead. For the deeplink problem that really suck... i hope you'll quickly find a solution. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#30 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC4XUCM7YTL4O6EDY5DFBBDSN5G47ANCNFSM4S4SPEOA>.