-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Pager not working in NS 5.1/Angular 7.1 #96
Comments
That’s a warning not an error does it crash ? |
Yes, unfortunately it does. Also, in Android I am getting [object Object], this is how my Pager looks like:
Thanks! |
Did you import the module ? |
Yes, i did. |
it works fine for me. All i get is a console warning... Make sure you import "PagerModule" in your app.module.ts
|
I've got the same problem. Module imported at app.module.ts |
Hey @ShyshkovOleg, I didn't solve it, I solved the situation using horizontal scrolling instead of this plugin. Maybe I should try again. |
Hello! I've the same situation as @relez and @ShyshkovOleg - I am getting [object Object] instead of content passing in ng-template. NS 5.1 and Angular 6.1. I'm sure that import works fine. Code example:
And result: |
@mdwe I am getting the same behavior if I add the Pager to the |
@mdwe This issue some how related with targeted API Level or AndroidManifest file. Because when I change Api level Plugin start to work as expected. And One more thing: |
This addressed the issue for me. |
Same for me in Angular 7.2.x and NS 5.4.x. I'm also using lazy loading for all child modules, but I'm not sure whether that has any effect. Adding it in any other module except the closest one to my component makes the entire app crash without any warnings or errors. |
Hi there, I am trying to implement a Pager in my app showing some images and since I updated to NS 5.1/Angular 7.1 I am having this issue once I try to navigate to the page where the Pager is:
Class "t41" already implements the "UIScrollViewDelegate" protocol.
I am using uglify/angular aot/webpack to run my app. I also updated to the latest version of the plugin (9.3.13).
Any help?
Thanks!
The text was updated successfully, but these errors were encountered: