-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_abandon
on Workflow
not actually called.
#41
Comments
NOTE: This is likely a low priority bug, as behavior on the user side is unaffected, #39 cleans up a fair amount of the references that Regardless, this poses no serious issues with the library. |
@Tyler-Keith-Thompson I think this is working now. I checked out main and set breakpoints in the places you mentioned and all of them got hit. I'm going to close this and you can reopen if you observe the behavior. |
Temporarily reopening while I make some sample apps and try to see if I can break this as mentioned in the exposition. |
Found when this happens! If you call abandon in the onFinish completion handler, self is nil. launchInto(workflow, args: "Noble Six", withLaunchStyle: .navigationStack) { passedArgs in // SwiftCurrent
workflow.abandon()
guard case .args(let emailAddress as String) = passedArgs else {
print("No email address supplied")
return
}
print(emailAddress)
} |
Found a fix for the bug. We just make our |
Describe the bug
There's a deceptive bit of code that looks like it functions, but in real world conditions is silently failing.
To Reproduce
Steps to reproduce the behavior:
_abandon
function inWorkflow
.Expected behavior
_abandon
should have been calledAdditional context
A quick and dirty fix, that I haven't investigated enough yet:
The text was updated successfully, but these errors were encountered: