do i think fire should adjust the project behind your back and set a deployment target that you did not set and did not test for, automatically? no, i don’t, and it won’t.
But, at a minimum, Fire should indicate to the user that field is empty. Do not you think? 
No, i don’t. An empty Deployment Target setting is perfectly valid, and the same as if it were set to the current SDK version. Why should Fire warn for that, and what would that accomplish? Your project would still fail, if you did set the deployment target tom say, 10.0 and tried to run on 9.3.
This is no different than, say, building a Windows app that uses Windows 7 APIs, and then tryingto run it on Windows 95. It’d crash, and badly. At least iOS does give yon the option of setting a deployment target.
Ok. Thanks Marc.
FWIW, i have fixed that it won;'t allow to run and deploy to a device with a lower version than the effective deployment target (derived from DeploymentTargetVersion, TargetSDK and the default SDK), now.
Yes, that’s perfect. Thanks.
1 Like