{"action":"opened","issue":{"url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport/issues/194","repository_url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport","labels_url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport/issues/194/labels{/name}","comments_url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport/issues/194/comments","events_url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport/issues/194/events","html_url":"https://github.com/MvvmCross/MvvmCross-AndroidSupport/issues/194","id":140945935,"number":194,"title":"Cached ViewModels (of fragments) don't re-run lifecycle when with a new navigation","user":{"login":"vvolkgang","id":542036,"avatar_url":"https://avatars.githubusercontent.com/u/542036?v=3","gravatar_id":"","url":"https://api.github.com/users/vvolkgang","html_url":"https://github.com/vvolkgang","followers_url":"https://api.github.com/users/vvolkgang/followers","following_url":"https://api.github.com/users/vvolkgang/following{/other_user}","gists_url":"https://api.github.com/users/vvolkgang/gists{/gist_id}","starred_url":"https://api.github.com/users/vvolkgang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vvolkgang/subscriptions","organizations_url":"https://api.github.com/users/vvolkgang/orgs","repos_url":"https://api.github.com/users/vvolkgang/repos","events_url":"https://api.github.com/users/vvolkgang/events{/privacy}","received_events_url":"https://api.github.com/users/vvolkgang/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-15T11:34:13Z","updated_at":"2016-03-15T11:34:13Z","closed_at":null,"body":"Creating an issue so I don't forget to PR this. If a fragment ViewModel is cached and re-used,it won't re-run the lifecycle with a new navigation.\r\n\r\n[Problem source](https://github.com/MvvmCross/MvvmCross-AndroidSupport/blob/master/MvvmCross.Droid.Support.V7.Fragging/Fragments/MvxFragmentExtensions.cs#L53) \r\n\r\nMy current solution was to change `MvxFragment.OnCreate` to also run the lifecycle for the cached one. Need to test this in the sample to figure if something more is required.\r\n\r\nThis might be related to #112\r\n\r\n### Steps to reproduce\r\n\r\nNeed to implement custom code in the sample to repro this.\r\n\r\n\r\n### Expected behavior\r\nViewModel should run his lifecycle again, receiving the new navigation parameters and updating the view with new info\r\n\r\n### Actual behavior\r\nGiven that the ViewModel is cached and didn't ran the navigation, the view will have the previous info.\r\n\r\n### Configuration\r\n\r\n**Version:** 4.0.0\r\n"}}