In my previous post I showed how to introduce search as type behavior into Xamarin.Forms app with standard Forms Behaviors.
Let’s see how to do it in other, more declarative and configurable manner, using Reactive Extensions (Rx) instead of Task and CancellationTokenSource.
Search as type functionality is quite often seen on the web as well as in mobile apps. Let’s see how to make it work in Xamarin.Forms.
All the credits for solution described in this post goes my friend qbus. He saved few hours of my life and my sanity ;-)
ModernHttpClient is a great wrapper around native HTTP clients offered by Xamarin. It wraps NSURLSession on iOS and OkHttp on Android. As it deals pretty well with SSL/TLS stack (especially in uncommon scenarios) it’s often used instead of built-in types. I switched to ModernHttpClient because of weird errors on connections to the preproduction environment in Android.
Have you ever encountered an error: Error executing task BuildApk: .../bin/packaged_resources does not exist? If so you probably know that solving this issue can be sometimes quite tricky. It may be hard to track when and where the true bug was introduced in the code base. Although some suggestions can be found on the Xamarin Forum the solution usually differ case by case.
An error Failure INSTALL_PARSE_FAILED_MANIFEST_MALFORMED appears from time to time in world of Android Java developers. However among Xamarin devs it seems to appear much rarely. Today I came across one and the standard Android solution did not work for me. Curious about the solution I found (with a little help of my friends)?
If you ever encountered the error AAPT: Unknown option '--no-version-vectors' during the Xamarin build you probably found this page looking for a solution. Like I did. Then you probably first tried setting AndroidSdkBuildToolsVersion to the latest you have. Just like me. Or uninstall all the older versions. If this didn’t work (like in my case) stay with me.
If you are using Azure Active Directory services you probably at least considered using ADAL as a client library in you application. It’s easy to setup, use and it offers a unified API across the most popular platforms - iOS, Android, UWP, web - both .Net and native. Unfortunately sometimes things just does not work out of the box without deeper understanding how some features are implemented. This post is about one of them - credentials cache persistency on iOS.
Working on a bug fix in MVVMCross-based mobile application I noticed a strange behavior. The navigation to other view model I put in async Init<TInit>(TInit parameters) which as executed on the first view model in my app was running twice. After a short debugging session it turned out that MvxViewModel<TInit> Init() is called from the view controllers ViewDidLoad() method. Obviously there was something I was missing in terms of ViewDidLoad() semantics.
Considering Xamarin there can be many reasons for need of screen resolution detection in mobile app. You may have more complex logic of loading your resources possibly split between PCL and Android/iOS projects. Other might want to send this information with REST request for reporting. Whatever your reason is, here is a very short text on how to do it in IoC-friendly way.