We have just fixed this issue in our latest developer's snapshot of Ext.NET Mobile!.. The fix will be publicly available in the next public Ext.NET Mobile release (4.2, no due date as of now), but it is already available for premium subscription users!