I have the same issue. In my case I tried to set focus immediately after the QInput was created with v-for.
I tried setting focus inside this.$nextTick but it didn’t work. The focus was set and immediately blurred.
I was able to make it work by setting the focus inside setTimeout:

AddItemToArray(item) //this adds an item which creates another qinput that is behind v-for
const _this = this
let fields = _this.$refs.myinput
setTimeout(() => {
  fields[fields.length - 1].focus()
}, 500)

Link has changed: https://quasar.dev/style/visibility#Window-Width-Related

basically lt- and gt- prefixes allow visibility on resolutions less than or greater than what is defined. E.g. lt-lg will be displayed on xs, sm and md

Link has changed: https://quasar.dev/style/visibility#Window-Width-Related

basically lt- and gt- prefixes allow visibility on resolutions less than or greater than what is defined. E.g. lt-lg will be displayed on xs, sm and md

@metalsadman said in Using Quasar components within an App Plugin:

.

For anyone who land here like I did, to call Notify this way you have to use the method create like this:
Notify.create('message')
or
Notify.create({message:'message', position:'top'...})

This is equivalent to calling
this.$q.notify()
from within a component

I have the same issue. In my case I tried to set focus immediately after the QInput was created with v-for.
I tried setting focus inside this.$nextTick but it didn’t work. The focus was set and immediately blurred.
I was able to make it work by setting the focus inside setTimeout:

AddItemToArray(item) //this adds an item which creates another qinput that is behind v-for
const _this = this
let fields = _this.$refs.myinput
setTimeout(() => {
  fields[fields.length - 1].focus()
}, 500)