static handleIncomingUrl

[OniQ]

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• All existing tests are passing
• Tests for the changes are included

What is the current behavior?

Uncaught TypeError: this.handleIncomingUrl is not a function

What is the new behavior?

Fixes #138

[alexziskind1]

I'm closing this as the original issue #138 is Android related and this PR targets iOS only. Furthermore, after testing, there is no such issue that I could reproduce on iOS.

[JohanBeumer]

@alexziskind1 Please consider reopening this PR. I'm getting the error only on iOS, but only in my own project in which I also use firebase. Putting the solution of this PR in place solves it.

However in the community chat of 23rd september starting at minute 13 @NathanWalker and @cjohn001 discussed #135 which is exactly what I am experiencing. So maybe there is a better solution?

Unfortunately I'm not familiar enough with delegates to be able to put the solution @NathanWalker suggests in place. Any help with that is appreciated!

Lastly I searched the code of the repo and handleIncomingUrl only is in the sources :
demo-angular/node_modules/nativescript-oauth2/delegate/delegate.ios.js
demo-angular/node_modules/nativescript-oauth2/delegate/index.ios.js
src/delegate/index.ios.js
src/delegate/index.ios.ts
so it must be an iOS thing, right?

[hammelev]

@alexziskind1 please open the PR again. The current version breaks my application when used together with the firebase plugin on iOS when attempting to login. Adding this PR fixes the error and allows my application to login.

[nc-kfl]

Nice work with this package for NativeScript @alexziskind1 and @OniQ. What are the changes that this can be reopned? On my project we have problems with the firebase plugin too and the fixed in this pull-request has shown to fix it.