Sometimes It has to match with the plugin version though dont think old versions of that is available ​​​​Eg 2.1sdk didnt work with 2.2 plugin
I found the issue .. the XML in the manifest file is formatted differently in the manifest files that it does not like.
If there is NO LINE between items as in .. products, permissions and languages for example, then it will not allow you to create a new run configuration. It will just choke on the manifest file.
Also on another I deleted the MinSDK part and it started to work.
Btw .. you would think that using the manifest editor would work, but it does not. The problems still remain.
The fix .. to add the needed blank lines in the manifest files where they do not exist and the problem goes away.
This is something that Garmin should fix .. as I should not have to manually edit my manifest files when updating to a new SDK.
I lied .. it only fixed one of my projects doing that, most of them give me the following error when I try to select it under run configurations. I am still sitting at 5 applications I cannot get to work. Maybe one of the Garmin guys will come in here and comment, and maybe fix their run configuration part so that it works.
Resource '/HR Tracker/manifest.xml' does not exist.
Garmin officials are likely busy with 2.3.4, but meanwhile can you try and remove the spaces from your folder names?
I reported a bug on that with the introduction of SDK2.2 (search the forum for blue arrow),... not sure whether everything related to projects with spaces in them have been fixed in the mean time (as I've moved on to folders without spaces now... )
Garmin officials are likely busy with 2.3.4, but meanwhile can you try and remove the spaces from your folder names?
I reported a bug on that with the introduction of SDK2.2 (search the forum for blue arrow),... not sure whether everything related to projects with spaces in them have been fixed in the mean time (as I've moved on to folders without spaces now... )
Cheers, Peter. My apps
No .. not an issue with spaces in my folder names. In one of my applications .. it was the lack of lines in the manifest file that was the issue. I added 3 lines between the XML and it fixed it. But I have 4 applications that I cannot create a run configuration. I have written a PM to one of the Connect IQ guys so that they can fix this.
VivoactiveHRGuy We'll definitely investigate this--thanks for providing an example file.
For the undetermined project type, check to see whether the <iq:application> item has a 'type' attribute with a valid app type (e.g. 'watch-app', 'datafield', etc).
The issue is absolutely that the SDK versions 2.3.x are unable to properly read the older manifest files (some but not all files) and just choke. There was no issue until the 2.3.x SDK's were released. However .. you can open the manifest files in the manifest editor and they show fine (with all the data on the screen being correct), but the run configurations still do not work and you will get the project type undetermined. Even editing and saving in the manifest editor will not fix the manifest files.
The only way I was able to fix my corrupted manifest files was to create a new manifest file by making a new Connect IQ project (in SDK 2.3.4) and copy and paste in the required data from my old manifest file. Btw .. if you look at the files, there is nothing you can see that is incorrect. I am going to just use 2.3.4 and hope the problem goes away.
Brandon .. I will find a manifest file that does not work (I have a backup of every version of all my apps since day 1 and should be able to find a manifest that it does not like) and email it to you.
