-
-
Notifications
You must be signed in to change notification settings - Fork 34
Documentation is not enough the call back is never called. #16
Comments
@scavezze you need to add |
@scavezze Did I need to add the JavaProxy decorator and the extend? |
@roblav96 it's already set to single task
I noticed 2 changes were made tho one for the docs and one other one so let me get the latest and try it out |
@hypery2k I think your really close i have tried whats currently avail and the following line throws a exception
I think don't think you need that and the
is called every time you receive a external link so i think you just need to remove that line then change handleIntent to something like this
|
I modified my local version to what i recommended above and it works but again it stops the ActionBar -> ActionItem event from working. gonna try and figure that out . |
ActionBar -> ActionItem event is not a issue with the linking. I think it's something with when i am changing routes in the handler |
maybe you have to wrap it in a zone |
https://gist.github.com/scavezze/28d2e69aa39b69796769d729fc1ee638 with the 0.4.0 version of your plugin works also so i will leave it upto you if you want to change to use protected onNewIntent(intent: android.content.Intent): void { or jsut add it to your documentation. I am new to Nativescript/Typescript so I will look into zones |
use event listener and add create event listener, see #16
I have followed the directions exactly. but the urlHandler never fires. I am running into this issue
NativeScript/NativeScript#3738
i have followed the directions above to cextend the native script activity but It precludes using your handler witch i really like because it helps pars the url and will work on ios. I tried adding
instead of
This solves the issue and i can use your plugin without issue unfortunately this seems to break the ActionBar -> ActionItem click event i am not sure why
have you run into these issues using your plugin? am i missing something. I would really appreciate your help.
The text was updated successfully, but these errors were encountered: