I have an application that pulls data from a web-service. This works as intended in the simulator. The app shows a list of some 20 patients.
The problem:
It only works fine in the simulator!
Testing the app after deployment going to the app's url in the IE brings up some errors (e.g. "Nullable does not contain a value" - maybe house-made error, I need to check), but catching them will show at least the page with the relavant information.
Chrome does not show anything!
When I run the app on a mobile device (browsing to the app's URL), the page comes up but is completely empty: This is the case for Android and IOS (same result as using Chrome).
If I start the application in the simulator and select the option "Final Version (pure JavaScript/HTML)" and select "Click to run in the browser...", the app's page is empty too (can only run in Chrome because of use of IsolatedStorage, which IE does not support when starting the app from file index.html): same result as running on mobile device.
Interesting to see is the following:
Having Fiddler run in the background, I can see that the request is sent via http-verb OPTIONS, resulting in no correct response for the app. The OPTIONS verb is only sent when using Chrome, IE sends POST!
I assume (but I don't know how to check at the moment) that the Android's browser (and I guess IOS' too) will also send the OPTION verb and not the POST like IE does.
The CORS settings in global.asax and web.config were made.
So I am really a little bit confused...
Did you experience same problems?
Any advices, tips, tricks I can use?
It is very important for us to make this demo-app runnable on mobile-devices...So....can you hear me crying ?
Harry