iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
Description
Hello Crosslight Team,
any sample which uses inventory data crashes when the culture on the device is not "US" or similar.
Step to Reproduce
Change the culture to "German" and try it.
Actual Result
Crash. Runtime Error.
Expected Result
Please, change the code in the ItemRepository.cs where the price is parsed from XML data to the following:
Price = decimal.Parse(x.Element("Price").Value, CultureInfo.InvariantCulture),
Thank you for the valuable feedback regarding the usage of InvariantCulture in ItemRepository.cs file. However, during my attempt to replicate the problem, the sample doesn’t crash.
Could you please kindly provide me with video which shows how to change the culture to “German” and the activity which causes the sample to crash?
Unfortunately I don't have any video capturing software installed. But I think you are the experts and you should know how to change the language settings on an iOS device. My settings are: language - German, region - Switzerland. In our region there is nor price format like "1'234.56".
Any view/activity which calls the ItemRepository to convert the Xml data to objects crashes.
If you cannot reproduce the bug, I don't care. I know how to fix the problem. I just thought it would be nice for other European developers because the cause of the crash is not obvious and from samples delivered with a product I wouldn't expect crashes.
Apologize for any inconvenience this problem might have caused you.
I have informed Crosslight Development team to fix the invariant culture on Inventory Data. The reason why I ask you to send a video, which shows the step to reproduce the sample crash, is to ensure that we don't miss a step to replicate the reported problem.
Thank you for the valuable feedback and have a nice day.
Edited on June 19, 2014 11:20 PMReason: Update Work Item Number
This problem has been submitted to Crosslight development team and filed under CROS-389.
Is this bug already fixed?
What is the current state of the bug, what priority has this bug, how can I check this?
We have recently released hotfix for Crosslight 2 Update 2 on June 30, 2014. The hotfix includes the fix for CROS-389.
To read the detail of what included in this hotfix, please check Crosslight 2.0 Update 2 Release Notes at http://developer.intersoftpt.com/display/crosslight/Crosslight+2.0+Update+2+Release+Notes.
Kindly check Updating Crosslight page at http://developer.intersoftpt.com/display/crosslight/Updating+Crosslight to get the detail information about how to obtain and apply updates to your project.
Please let us hear your feedback whether it helps or not.
CROS-389 is not mentioned in the fix list. How should I have a chance to see if this bug is fixed?
The fix for CROS-389 is implemented in ItemRepository.cs file of MyInventory and MyInventory_MasterDetail sample project. Please check the file in the Develop branch.
Thanks Yudi,
I think we can close this bug.
Glad to hear that the fix in ItemRepository.cs resolves the reported problem.
Should you need further assistance or run into any problems regarding our controls, feel free to post it into our forum. We would be happy to assist you again.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname