PropertyChanged.Fody + MvvmCross 6.2 = crash
See original GitHub issueCombining PropertyChanged.Fody with MvvmCross 6.2-beta results in crashing with System.InvalidProgramException: Invalid IL code in MyApp.Core.ViewModels.LoginViewModel:set_RememberMe (bool): IL_0020: ret
see: https://github.com/MvvmCross/MvvmCross/issues/3016
Probable Solution: Properly handle Task-returning as well as void-returning RaisePropertyChanged()
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Commit d2a7fb2d on June 15 breaks compatibility with ...
Fody. Old (and correct) behavior. MvvmCross played nice with PropertyChanged.Fody without crashing up through Mvx6.1.2. Current behavior.
Read more >MvvmCross 6.2
Announcing MvvmCross 6.2! ... If you are using Fody. ... raised in event handlers for PropertyChanged won't make your app crash anymore.
Read more >MVVMCross v6.2.0-beta3 release notes (2018-08-17) | LibHunt
MvxTabbedPagePresentation with WrapInNavigationPage = false crashes when closing a ... Commit d2a7fb2d on June 15 breaks compatibility with PropertyChanged.
Read more >Is it safe to use Fody.PropertyChanged with MVVMCross ...
Today I read about new plugin on net which Fody.PropertyChanged which is very simple and easy to use. Currently I am using MVVMCross...
Read more >hujinguang/MvvmCross
FormsApplication #2832; Fix crash and improve MvxRecyclerViewAdapter ... Init() in android renderer in mvvmcross 6.2 #3262 ... Fody #3016 ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ltrzesniewski That worked perfectly. Thanks!
I’d say you need to modify this method so it returns
IEnumerable<Instruction>
instead ofInstruction
(fix the call sites, obviously), and if the method returns something other thanSystem.Void
, then just add apop
instruction after thecallvirt
.This would simply ignore any return value (even if not a
Task
), which I think is the right behavior.