You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"TabsAction.profile(.onAppear)" was received by a reducer when its state was unavailable. This is generally considered an application logic error, and can happen for a few reasons:
The reducer for a particular case of state was combined with or run from another reducer that set "TabsState" to another case before the reducer ran. Combine or run case-specific reducers before reducers that may set their state to another case. This ensures that case-specific reducers can handle their actions while their state is available.
An in-flight effect emitted this action when state was unavailable. While it may be perfectly reasonable to ignore this action, you may want to cancel the associated effect before state is set to another case, especially if it is a long-living effect.
This action was sent to the store while state was another case. Make sure that actions for this reducer can only be sent to a view store when state is non-"nil". In SwiftUI applications, use "SwitchStore".
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Getting this warning
TabView > ProfileView > SettingView
Warning: Reducer.pullback@AppFeature/AppView.swift:63
"TabsAction.profile(.onAppear)" was received by a reducer when its state was unavailable. This is generally considered an application logic error, and can happen for a few reasons:
The reducer for a particular case of state was combined with or run from another reducer that set "TabsState" to another case before the reducer ran. Combine or run case-specific reducers before reducers that may set their state to another case. This ensures that case-specific reducers can handle their actions while their state is available.
An in-flight effect emitted this action when state was unavailable. While it may be perfectly reasonable to ignore this action, you may want to cancel the associated effect before state is set to another case, especially if it is a long-living effect.
This action was sent to the store while state was another case. Make sure that actions for this reducer can only be sent to a view store when state is non-"nil". In SwiftUI applications, use "SwitchStore".
from https://gist.github.com/saroar/44a5dece186e4bd50e8dd2aa9cab79f6#file-appview-swift-L106
AppView2-2.mov
Beta Was this translation helpful? Give feedback.
All reactions