Tiago Alves

Hi! I just found this issue and I want to say that `vuexfire` TOTALLY WORKS with `nativescript-plugin-firebase`. @ibonkonesa if you want, I can show some code, but I basically followed...

Yes. There is a small difference that `nativescript-plugin-firebase`'s init method does not return a firebase instance.

Try this: instead of using `mounted()` use the `@loaded` event on the page, (or another component). E.g: ``` methods: { loaded() { // the stuff you were doing in mounted...

@Myastroo, make sure you have the line ``` Vue.config.silent = false; ``` in your `main.js`.

Hi! Try moving the font from `/app/assets/fonts` to `/app/fonts`. Since you have `TNSFontIcon.debug = true;`, do you see a bunch of icons being loaded in the logs?

Hi! That's not the correct way to pass props. See here: https://nativescript-vue.org/en/docs/routing/manual-routing/#passing-props-to-the-target-component It should be: ``` this.$navigateTo(Second,{ props:{ id: 14 } }); ``` Also, you need to declare the prop...

This bug happens in several cases when using Vue ``s. I think @rigor789 is correct and NS is triggering the animations twice when changing the class. More specifically, I think...

Hi! I did install the plugin correctly and it **does work** when I don't add `use_frameworks!`, like so: ``` source '[email protected]/CocoaPods/Specs.git' platform :ios, '8.0' #inhibit_all_warnings! def common pod 'WeexNatDeviceInfo', '1.0.0'...

@Acathur you mean like add them without cocoapods? which library?

I can do that. But then we also need to add a `none` option to the theme, right?