You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use e.g. MvxViewPagerAdapter for the view pager. Initialize it with a single-element collection MvxViewPagerFragmentInfo object that contains a view model INSTANCE which cannot be directly resolved from the IoC container (e.g. it is manually created with parameters from the parent page view model)
Try to open that page
💥
Expected behavior 🤔
Both MvxViewPagerAdapter and MvxStateViewPagerAdapter should check whether the fragment info already contains the view model instance, and if yes, do not try to Mvx.Resolve that.
Actual behavior 🐛
Crash with a dependency resolution exception.
Configuration 🔧
Version: 5.7.0
Platform:
📱 iOS
🤖 Android
🏁 WPF
🌎 UWP
🍎 MacOS
📺 tvOS
🐒 Xamarin.Forms
The text was updated successfully, but these errors were encountered:
I would like to contribute under this issue separately, because I don't yet feel the strength to completely clean-up these adapters in the scope of #2440 . I am currently preparing a PR.
wh1t3cAt1k
pushed a commit
to wh1t3cAt1k/MvvmCross
that referenced
this issue
Mar 23, 2018
Steps to reproduce 📜
Use tab layout with a view pager.
Use e.g.
MvxViewPagerAdapter
for the view pager. Initialize it with a single-element collectionMvxViewPagerFragmentInfo
object that contains a view model INSTANCE which cannot be directly resolved from the IoC container (e.g. it is manually created with parameters from the parent page view model)Try to open that page
💥
Expected behavior 🤔
Both
MvxViewPagerAdapter
andMvxStateViewPagerAdapter
should check whether the fragment info already contains the view model instance, and if yes, do not try toMvx.Resolve
that.Actual behavior 🐛
Crash with a dependency resolution exception.
Configuration 🔧
Version: 5.7.0
Platform:
The text was updated successfully, but these errors were encountered: