2.3.1 Build Problem .. Unable to Find Exact Match

Not seen this, but as a guess, do you have a min SDK version in your manifest.xml by any chance?

Not seen this, but as a guess, do you have a min SDK version in your manifest.xml by any chance?

Yes .. but removed it and it made no difference. I have major issues with this SDK .. and am going to have to restore my pc from a system image to revert to before this SDK. It is that messed up .. I cannot even go back to an old SDK like I used to be able to. I am ok with it .. as I have no need to ever go to more than 2.2.6.

Did you also update the Eclipse plugin if you weren't running the BETA SDK?

It's the '-s 2.1.0' portion of the build command. Is this in Eclipse, or do you use your own build scripts? If you use Eclipse, have you updated the plug-in?

In the 2.3.1 SDK, the 2.1.0 SDK is no longer a valid target for the vivoactive HR (worldwide devices are on 2.3.x, and APAC devices are on 2.2.x), so that's why you're seeing the error when a target of 2.1.0 is specified. I'm just not sure why you're getting a 2.1.0 target.

Thanks Brandon .. this is 100% eclipse generated scripts.

The only thing I did was install the 2.3.1 SDK and install the Eclipse updates.

This is an non issue for me as I am going back to 2.2.6 .. but others may have issues so this should be looked into. I see that my run configs are all messed up after upgrading and I cannot recreate a new one .. as it does not work.

Edit .. I am back running 2.2.6 and all is working fine. Good thing I do nightly backups. :)

Hey VivoactiveHRGuy,

It looks like you just need to update your run configuration. I don't typically use them because I'm testing a lot of different devices so it doesn't make as much sense for me, but I can see how that would be useful. Eclipse stores your run config with all the parameters you set. I tried rolling my sdk back to 2.2.6 and setting a run config with a 2.1 target. Then I switched to the 2.3.1 sdk, used ran that config, and saw the same thing you did. This is because Eclipse is just feeding the run the parameters you set up originally (in this case a 2.1 target) resulting in the error. All I had to do was open the run configuration. Once the dialog is open it will update the targets to 2.2 and 2.3 for the currently selected SDK (2.3.1). I just hit "Run" from the dialog and it saved all the new parameters. After you update it, you can hit F5 'till the cows come home without error. :D I hope this helps. If you use run configs heavily, this may explain some of the other issues you were seeing.

Thanks!
-Coleman

I'm 99% sure the cause of viv's issue is this: https://forums.garmin.com/showthread.php?377882-Install-2-3-1-SDK-manager-does-not-update-plugin

Thanks Coleman .. but the problem was that once I upgraded, the run configs seemed to be corrupted and did not work right. I even tried to create a new one .. and I could not do that.

As almost all my apps are for the Vivoactive HR (the only device I own, and unlike many I do not make apps for the whole range of devices), I use run configurations exclusively. It just makes running things very simple.

I could not recreate a new config .. as it picked the wrong project after I selected the right one, and the Target Device and Target SDK showed as invalid and I could not change them.

I exclusively use the SDK manager btw .. but I will leave this issue to the Garmin guys to look at if they desire.

Just a note .. I just tested with 2.2.6 and everything (run configs and running apps in the simulator) works fine, but it appears that 2.3.1 has some issues .. and probably Peter is on the right track for those of us that use the SDK manager.

I had this exact same problem just now upgrading to 2.4.3 and Coleman's suggestion worked perfectly for me