ERA leads to question: Are there problems with 9.50 FW for Edge 1030?

Hi,

Trying to work out whether I need to do anything about an ERA report.

The error report is not very interesting or explanatory:

Error Name: System Error
Occurrences: 1
First Occurrence: 2020-06-09
Last Occurrence: 2020-06-09
Devices:
    Edge® 1030: 9.50
App Versions: 0.0.18
Languages: deu
Backtrace:
    DataField_SingleDialBaseView.initialize:317
    DataField_SingleDialBaseApp.getInitialView:19

Which equates to this code:

do { // Create session and lap couhts
	obj[:mesgType] = mType;
	fitFields.add(createField(fieldLabStub+id, id, dataType, obj));
	id++;
	mType++;
} while(mType < 20);

The line number is the "do {" which means that something probably happened during the loop, and the createField is the most likely issue because... createField is always the most likely issue. I've seen similarly anonymous errors for createField...

#HINT PLEASE VOTE FOR THIS ISSUE! https://forums.garmin.com/developer/connect-iq/f/app-ideas/223155/please-can-the-next-sdk-give-more-meaningful-errors-session-createfield

However, this code has been there since the beginning and the memory limits that can cause issues should not affect an Edge 1030 that has four times the memory I built for. And the number of field limits that I am guessing at based on experience and various thread discussions [in the absence of any documentation from Garmin on same] should be comfortable for Edge 1030, too. (And hadn't previously caused issues after being live for several months.)

#HINT PLEASE ALSO VOTE FOR THIS ISSUE! https://forums.garmin.com/developer/connect-iq/f/app-ideas/229872/please-can-the-sdk-documentation-be-more-developer-friendly-and-searchable-and-complete

Finally, I checked the FW version which looks to be the most current version... In doing so, I saw a number of error reports in the forum for the 9.5 FW.

Has something changed?

Is this my bug or Garmin's bug?

0 xuxumatu over 4 years ago in reply to 9635560

let me list all things I have done to fix this maybe we can get ideas to fix it but yes garmin misses info

convert setData to numbers
convert setData to floats
convert setData to nothing
setdata to null
use an if (currentTime) on createFields to wait to get data (that worked but not with all devices)

https://forums.garmin.com/developer/connect-iq/f/discussion/245620/initialize-error

invert jungle operations to see if the error it´s only on base source
build in 3.1.8 3.1.9 3.1.2 sdk
displayingactivitylaps all false
change precision numbers
deleta all languages
use typeuint16, typefloat, typesint
and all this
https://forums.garmin.com/search?q=least&group=35#serpq=least

remove rezstrings and put the strings directly

remove units
https://forums.garmin.com/developer/connect-iq/f/discussion/243137/fit-contributor-units/1167284#1167284

and the init error stills there on era not on simulator

and what is worst is that 3.1.3 sdk has no weather for edges you can not event think on test a weather related fit contributions on simulator, you have to use betas and on real devices

0 9635560 over 4 years ago in reply to xuxumatu

xuxumatu said:
you can not event think on test a weather related fit contributions on simulator, you have to use betas and on real devices

Surely, from a debug perspective, you can hard code some data to contribute and then send that in as a functional test?

0 xuxumatu over 4 years ago in reply to 9635560

yes you can on the beta option, you do need approval but ony you can see it and it also works with ERA

0 xuxumatu over 4 years ago

After several several several test this is a garmin error for sure all errors come from new 1030plus 530 and 830 no other devices, where can i report?

0 Horsetooth over 4 years ago

fwiw i've gotten a system error report in ERA that points to a line where i do 1 createField call from the initialize() routine of a data field, no loops...

Error Name: System Error
Occurrences: 3
First Occurrence: 2020-12-12
Last Occurrence: 2020-12-12
Devices:
fÄ“nixÂ® 6 Pro / 6 Sapphire / 6 Pro Solar / 6 Pro Dual Power / quatixÂ® 6: 13.10
App Versions: 0.1.3
Languages: eng
Backtrace:
NightscoutDataView.initialize:59
NightscoutDataApp.getInitialView:81

bgFitContribField = createField(
fitlabel,
BGFITCONTRIB_FIELD_ID,
FitContributor.DATA_TYPE_FLOAT,
{:mesgType=>Fit.MESG_TYPE_RECORD, :units=>"bg" }
);