Crash after removing current visited bot

[aksonov]

Error in tinyrobot

Error in node_modules/mobx-state-tree/dist/mobx-state-tree.js:1931
[mobx-state-tree] This object has died and is no longer part of a state tree. It cannot be used anymore. The object (of type 'Bot') used to live at '/wocky/bots/storage/98160d3a-4a49-11e8-9473-0a580a02051b'. It is possible to access the last snapshot of this object using 'getSnapshot', or to create a fresh copy using 'clone'. If you want to remove an object from the tree without killing it, use 'detach' instead.

View on Bugsnag

Stacktrace

node_modules/mobx-state-tree/dist/mobx-state-tree.js:1931 - Object

View full stacktrace

Created automatically via Bugsnag

[mstidham]

I received bugsnag and not sure what caused it but will list the previous actions taken:

1. Logged out of @miranda account
2. Did a kill/reload
3. Logged in bypass account @TestyTester and deleted a bot
4. Logged out of bypass account and did another kill/reload
5. App loaded to the signin screen and at that time I received the bugsnag.

[mstidham]

I just received this bugsnag while trying to test ticket #2247. Deleted a bot a received app crash on @TestyTester account.

[southerneer]

This doesn't happen on every bot delete, correct?

[zavreb]

This doesn't happen on every bot delete, correct?

Returning to previous name due to lack of certainty.

[zavreb]

Needed to test #2247

[mstidham]

@southerneer I just reproduced this on a presence bot that the user is currently a visitor. If you delete the bot from the widget the app crashes. I have not tried this with regular bots but will try that now.

[zavreb]

Per @mstidham on #qa, link:

I deleted Ace Lumber instead of Softball and had no issues.

[southerneer]

Then does this mean #2247 is good to go?

[mstidham]

Codepush Verified Staging-Pavel "#2225, #2248, #2244

[mstidham]

Verified on Staging Version: 2.6.3
Although I did not logout of device and log in as another user. Wonder if this is what caused the zombies.

[zavreb]

😍 Verified on Staging Version 2.6.3

[zavreb]

Verified on Prod 2.6.7

[mstidham]

Verified on Production Version: 2.6.8

[southerneer]

this one popped up again on Prod 2.6.8 today. Bugsnag reports that the app was in the foreground for 2 days (!) before the crash...hopefully an edge case that we can safely ignore.