-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nativescript 3.4 Ng 5.* compatibility #13
Comments
Thanks for the report, I'll take a look! |
Looks like the I've changed the internal logic to check for the Available in 2.1.1. |
Thanks for quick response Eddy, Nfc instantiation give no error, but somehow I get following error when I start adding ndefListener (using demo included in this repo)
|
Thanks, can you give 2.1.2 a try? |
Great, it now works as expected Thank you very much :) edit |
Still same issue here :
with a service like this :
|
Still stuck with the same issue as @kriefsacha, @EddyVerbruggen Any clues? |
I create a new instance every time i need @GijsPost .. |
I'm seeing exactly this same issue with latest version of all software components:
It appears to happen consistently on first-run after compiling and installing the app. I'm using nativescript-angular and webpack. I've tried instantiating in a public variable, constructor and ngOnInit, but the error still appears. Error occurs on instantiation: Not sure where to go with this apart from perhaps catching the error and ignoring it. Any further help would be appreciated. |
Share a repo and I might find some time to look into it. |
@glydetech as i saied i used a new instance that i created everytime in a function and it worked.. |
Hi Eddy,
sorry to disturb in this holiday season, but it seems after I update my tns to 3.4, nativescript nfc is now broken.
So I tried to create new project using
tns create sample --ng
, modify the sample page to looks like this, and got error.It seems that we can not access application.android.foregroundActivity in NS 3.4
template
component
error
The text was updated successfully, but these errors were encountered: