Implementing a queue: Transitioning to state X from another state machine is not possible #85
Answered
by
nsk90
reactormonk
asked this question in
Q&A
|
This is the child machine which handles messages from/to an external bluetooth device, however sending an From a level higher triggers I only have one |
Answered by
nsk90
Jan 25, 2024
Replies: 1 comment 6 replies
|
Typically this exception is thrown if transition targets state from another different state machine If you have only one state machine and single invocation of createStateMachine, maybe your machine was recreated because of android configuration change, (effectively this is another StateMachine instance in such case)? Otherwise this could be false triggering of an error. Minimal sample that reproduces the error could help. |
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes you can pass your data along with Events and store it in States (states are mutable by nature).
I dont think that DataExtractor is suitable for data transformation. DataState+DataEvent api is a implementation of typical data-passing use case. If it is too strict and does not fit your needs, you can use simple States and Events just storing your data in State fields and updating its manually from incoming Events.