I can confirm that my watch face (Crystal Tesla) doesn't read custom complication since CIQ 7. It works correctly if I compile with CIQ 6.4.2. Also, when running the watch face in the simulator (tried simulating a Fenix 7S Pro and FR 965), when it's time to iterate to my (or any other) custom complication, it fails with this message
"Command failed: D0 4 f1, bad response: 20005536,800153 1 47:800D4E 4 E9 800D4F 3 EB:800D50 3 EF:800D51 0 0:800D52 0 0:800D53 16 BE20:800D54 9 0:800D55 1 3"
This the code I'm reading the complications with
var complicationId = iter.next();
while (complicationId != null) {
//DEBUG*/logMessage(complicationId.longLabel.toString());
var type = complicationId.getType();
if (type == Complications.COMPLICATION_TYPE_HIGH_LOW_TEMPERATURE) {
/*DEBUG*/logMessage("Last one before us");
}
if (type == complicationType && type != Complications.COMPLICATION_TYPE_INVALID) {
/*DEBUG*/logMessage(complicationId.longLabel.toString() + " available");
complicationId = new Complications.Id(complicationType);
break;
}
else if (type == Complications.COMPLICATION_TYPE_INVALID && complicationId.longLabel != null && complicationId.longLabel.equals(complicationName)) {
/*DEBUG*/logMessage(complicationId.longLabel.toString() + " available");
complicationId = complicationId.complicationId;
break;
}
complicationId = iter.next();
The simulator fails at the "complicationId = iter.next();" when it's time to read my custom complication.
See here for detail
https://forums.garmin.com/developer/connect-iq/f/discussion/378515/has-something-changed-in-a-recent-ciq-regarding-passing-custom-complications-to-watch-faces
