You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After "upgrading" several library to include a corresponding library.properties file and instally Teensyduino which installs builtin libraries, I get many very unhelpful errors:
Maybe include a string of the library/platform name to VersionHelper.valueOf to make this message more informative? This is especially hard to do in VersionComparator.java as the Java Comparator doesn't allow something like that. But otherwise it is impossible to track down what causes these errors.
Invalid version found:
Invalid version found:
Invalid version found:
Invalid version found:
Invalid version found:
Invalid version found:
Invalid version found:
Invalid version found:
Invalid version found:
Invalid version found:
Invalid version found:
The text was updated successfully, but these errors were encountered:
Upvote. I wasted a lot of time solving an "Invalid version found:" problem due to a library that had a space in the version string in its library.properties file. The offending string was displayed in full but without a clue as to where this string resided. Using aduino_debug I got off in the wrong direction because the error showed up right after "Preparing boards...". If only it displayed something like "Loading libraries...". Just adding "library" to the message "Invalid version found:" would already help a lot.
per1234
changed the title
"Invalid version found:" with library name
"Invalid version found:" error message doesn't provide the library name
Aug 24, 2018
After "upgrading" several library to include a corresponding library.properties file and instally Teensyduino which installs builtin libraries, I get many very unhelpful errors:
Maybe include a string of the library/platform name to
VersionHelper.valueOf
to make this message more informative? This is especially hard to do in VersionComparator.java as the Java Comparator doesn't allow something like that. But otherwise it is impossible to track down what causes these errors.The text was updated successfully, but these errors were encountered: