I certainly agree, installing new versions of Xamarin is always a gamble. Although I must say, it has gotten somewhat better than it used to be. Maybe Xamarin should encourage their developers to work on their own projects using Xamarin during some hours a week. There has been some bugs which are so impactful I can't believe they actually use the product themselves.
Have you reported all these problems? One problem Xamarin do have is people complain about an issue but never report it. They can't fix what they don't know...
It feels like they sometimes just ignores bug reports as well. What's up with this, reported in 2015? https://bugzilla.xamarin.com/show_bug.cgi?id=36593
Maybe @JonDouglas knows anything?
Hi, I have got a quite similar problem.
I implemented the library and it seems to work fine except one thing.
After pressing a scan button my events are not raised...
I might think of a keycode to rais my events but in the sample code there are no too.
Do i miss any permissions or has it to work like that ?
I'm guessing you either forgot to call Claim on the reader or you're missing permissions.
The sample calls barcodeReader.Claim() in OnResume and barcodeReader.Release() in OnPause in the activity where you do the scanning.
Make sure to add the permission "com.honeywell.decode.permission.DECODE" to your Android manifest.
Only my Windows folder is 38GB at the moment, so 50GB for Windows AND VS, Xamarin, Android, Java etc is probably a bit on the small side.
If anyone has problems deploying to the emulator after upgrading Xamarin, go into settings and then apps on the emulator and make sure to uninstall the Xamarin stuff there. Uninstall your app, Mono Shared Runtime and Xamarin.Android API-XX Support.
We never had this problem before, but now it started occuring (at low rate).
Out of my head, only related thing changed was adding second server connection service that 'could' potentially be called during, or right after first service is complete with server api calls.
Could someone confirm similar scenario possibility?
This is my observation as well. I can reproduce it sometimes by starting a task with a HttpClient request, and immediately starting another task with another HttpClient request (different HttpClient objects).
There could be other problems as well, but this seems to be one of them at least.