Readonlyexpected: stringThe screen id, or the ids the entry may lead to, joined with , .
Readonlyfound: stringThe screen in front, or (no screen) when there is none.
Readonly_Readonly~effect/Optional Readonly~effect/Attach extra key/value metadata to this error.
Optional Readonly~effect/Suppress reports for this error.
Optional Readonly~effect/Override the severity level for this error.
Optional Readonly~effect/Optional Readonly~effect/OptionalcauseReadonlyexpectedThe screen id, or the ids the entry may lead to, joined with , .
ReadonlyfoundThe screen in front, or (no screen) when there is none.
Optionalstack
The app shows a screen the call cannot get past:
mainreceives the screen the entry names (screen:), or one of the first screens its stored value can lead to, and every other screen the app can land on — a challenge the server raised over an effect of the start or ofmain— is described once inotherwise, the branch that answers it. A screen is unexpected when no branch covers it, when its branch ran and the app is still on that screen afterwards, and when the effect the challenge interrupted, run again after the challenge closed, is interrupted again (no loop): the call has nothing left to try.Typed, because which screen the app shows is the server's decision (a challenge is the server's, not the caller's); the fields name the screen the call expected and the one the app shows, so a caller can add the branch (or name the screen it means) and run again.
expectedis the screen the interrupted effect ran on, or — over the start, before any screen is open — the screen id the entry names or the ids its stored value may lead to, joined with,;foundis the screen in front, or(no screen)when the app shows none.Raised by the Android entries only (
AndroidIgpapi), whereotherwiselives.