The Vuex State variables doesnt update. It just stays with the initial values.

[zuaaef]

Version

6.0.0-beta.11

Browser and OS info

MacOS catalina 10.15.4 (19E266) with google chrome Version 90.0.4430.212 (Official Build) (x86_64)

Steps to reproduce

I have to use console.log() as a workaround for me to see the values. I just run the app, and update values in the Vuex Store.

What is expected?

values in state should update

What is actually happening?

values stay the same as default -> https://user-images.githubusercontent.com/18083923/119898167-77304980-bf0f-11eb-8d89-f076e2edec97.png

[zuaaef]

i also tried it on Firefox, so i dont think it is browser related.

[Akryum]

Please provide a reproduction of your issue so I can run it and find where the problem is.

[zuaaef]

I have a huge app.. i'll try to create a smaller app which reproduces the bug.
but in the main time not sure if this is the issue?

const getDefaultState = () => ({
  navStackData: {
    indexData: {
      data: []
    },
    trendData: {
      data: []
    },
    feedData:{
      data: []
    },
    meData:{
      data: []
    }
  }
})

export const state = getDefaultState

My state looks like this. I did it this way so that i can reset to default easily whenever i need to.
Also i am using nuxt (but i doubt thats the problem).

If this information doesnt help, then let me know and i'll try to create a sample app some time in future if im free.

[zuaaef]

more info:

You can see that even though the state is still incorrectly on default value,
the getter is correctly on updated values

[Akryum]

What happens if you click on the refresh button on the top right?

[zuaaef]

If i click on the refresh button, the state still shows the original value.
it is not updated. The getters however are always updated correctly even without clicking on the button.

[dflock]

This happens to me too - it makes it really hard to see the "current state" of the store. If I have actions or mutations I can see them in the timeline view, but the inspector always shows me the initial state, not the current state; the refresh button doesn't do anything.

This is using:
Vue Dev Tools 6.0.0 beta 14
Chrome Version 90.0.4430.212 (Official Build) (64-bit)

[m4heshd]

@dflock I'm racking my brain trying to find the "force refresh" button. I thought the beta version doesn't have it. How come everybody else have it and I don't? Is the refresh only available for Vuex now?

[dflock]

Just "refresh" not "force refresh", afaik.

It's the little refresh icon in the top right of the devtools window - you can see it in the screenshot at the top of this thread:

[m4heshd]

Just "refresh" not "force refresh", afaik.

@dflock It's referred to as "force refresh" by the core team pretty much everywhere. So I just assumed it's the correct terminology and I think it is correct since it's literally forcing the refresh even though it's supposed to update automatically.

It's the little refresh icon in the top right of the devtools window - you can see it in the screenshot at the top of this thread:

I do know where it's suppose to be and I've used it a lot before because it doesn't update for events that doesn't trigger a re-render. But it's not there anymore. Since Vue 3 for me. 🤔 I just got used to using less and less of Vue devtools because of this issue but I'm doing a massive refactoring right now and this is bothering me very much.

[Akryum]

@m4heshd I guess you are talking about something different. If you have an issue with component data not updating automatically, please open a new issue. In the meantime, you can "force refresh" a component by clicking on it again in the component tree.

[m4heshd]

you can "force refresh" a component by clicking on it again

@Akryum OMG thank you. I don't know how I didn't notice that because I tried pretty much everything. This makes my life a lot easier. Awesome.

[patchthecode]

Hey guys,
i opened this issue 20 days ago.
I dont know when it started working, but it just started working across all my browsers 🤔.
I dont remember updating the plugin (or does it do that automatically?) but now i have version 6.0.0 beta 14 and it works as expected.

Maybe all you other guys can check to see if it works for you now?

I'll close this issue in a couple days.

[patchthecode]

i see @dflock says he is also using version 6.0.0 beta 14 and it is still happening.
did i close my browsers and restart them? no clue.
but it just suddenly started working.

[patchthecode]

Ok. I know why mine suddenly started working.
Its because I stalled ViteJS. When ViteJS is installed, everything works as expected, but once ViteJS is removed, the problem returns.