Issue #149 is due to use flow to set multiple FriendListScreens. But each FriendListScreen has the same scope name, so the scope might be destroyed after you enter next FriendListScreen.
This pull request use the object instance name as scope name rather than use class name should fix the problem.
Issue #149 is due to use flow to set multiple FriendListScreens. But each FriendListScreen has the same scope name, so the scope might be destroyed after you enter next FriendListScreen. This pull request use the object instance name as scope name rather than use class name should fix the problem.