Can't Track Down BUILD Errors--Including Assembler Errors

It is driving me crazy trying to find the cause of certain build errors. None of the errors specify a file (like a .mc file) and I have searched over all the files in my Eclipse project, tried clean building, updating all Eclipse Connect IQ apps, looking at the bin/xxx.prg.debug.xml file, checking the manifest.xml file, but no hints on what is causing the errors. One big mystery is it complains about fields like "NonstopWatch1", and "globals", which I can find no references to. Thanks for any help you can give me!!

Here are the details:

Eclipse: Oxygen.3a Release (4.7.3a), Build 20180405-1200
OS: Mac 10.13.4
Java: jdk1.8.0_131
Connect IQ: connectiq-sdk-mac-2.4.5

Build Output

See attached build-results.txt file. I couldn't get this forum's interface to allow the results in-line (Preview gets errors).



Manifest File

See attached manifest.xml file. I couldn't get this forum's interface to allow the xml in-line (Preview gets errors).
  • Yes, it is.

    The strange thing is that the original datafield (DatarunppremiumApp) builds fine with the midrange watches. The midrange watches have a different resourcepath, in the sourcepath are some files shared with the high end watches. The background process is for the Tempe; that is new for the update, and the storage function is also new.

    The copy version has one variable more and memory and objects are tight. It might be that the compiler is behaving strangely because of that?

  • So, finally found it. I had created a 2nd baseApp file, for the midrange watches with the last update of the main version. My monkey file pointed towards the directory it was in, but I completely forgot about it and didn't also change "class DatarunpremiumApp extends Toybox.Application.AppBase {" in "class Datarunpremiumwith7metricscopy2App extends Toybox.Application.AppBase {" there.

    Jim was right, as he always is. Now if only the compiler could give the hints that Jim does... Slight smile