12-14-2017 15:28
12-14-2017 15:28
I suspect Studio reports code line numbers against a transpiled file (.ts?) rather than against the user's source code. This makes debugging more difficult. Would it be possible to investigate and correct this?
If source code line numbers can't be reported, it would be useful to see the transpiled code line that is causing the problem (eg, as part of the error message). This would provide a strong clue about where to look.
12-15-2017 08:40
12-15-2017 08:40
If you download the package you can open the compressed file and you will see "index.js" in the app folder, that is the compiled file and the error line numbers refer to that file.
A bit of a pain to keep doing it, but it can help.
12-15-2017 12:17
12-15-2017 12:17
Outstanding! Silly me never thought to look there. That will help a lot. Many thanks.
10-29-2018 12:09 - edited 10-29-2018 12:12
10-29-2018 12:09 - edited 10-29-2018 12:12
You used to be able to select the error link and it would take you to the correct line. It is quite annoying that the studio no longer equates to the error.
The line code of the downloaded file still does not match (it gives an error for a variable that is not referenced on that line). Any other ideas?
10-29-2018 14:34
10-29-2018 14:34
Sounds like you are having the problem reported here: https://community.fitbit.com/t5/SDK-Development/Line-numbers-off-with-simulator-and-online-builds/m-...
10-31-2018 10:11
10-31-2018 10:11
Yes sir.
They did not address or fix it there, either.