ERA/Fenix6???

For six months, I have had no ERA reports from my previous versions. None. Zilch. Nada!

On June 6 I released a new version(4.1.3)

Today I find 4 ERA reports for the new version.

This app version 4.1.3 has been

running since June 6
on over 300 watches globally
across 48 different products,
but has only reported crashes on 3 products: fenix6, Fenix6 S and fenix6 Pro,
at four code points,
all of which are within the highly trafficked regions of the app.
There is far too little detail in the crash report to enable any debugging.

device	Occurrences	first	last
fenix6	5	2022-06-24	2022-06-24
fenix6 S	1	2022-06-24	2022-06-24
fenix6	4	2022-06-28	2022-06-29
Fenix6 Pro	1	2022-06-30	2022-06-29

As a mathematician, but not an epidemiologist, I find this result highly questionable.

Can anyone offer a similar experience?

Is there an incompatibility between the F6 and ERA?

BobMiles over 2 years ago

Is there maybe a firmware version on the Fenix 6 that has problems with your app? I see some crashes for my watchface on epix devices that still have the stock firmware, the code points are very inexplicable, too.

So what about the firmware versions in your reports?

Alan.raceQs over 2 years ago in reply to BobMiles

All of the Fenix 6's were reporting running 22.10 Not sure how to find out current versions for Fenix 6. Best I can find is https://www8.garmin.com/support/download_details.jsp?id=15031 indicating 20.50. So what's that all about?

OttawaDeveloper over 2 years ago

I had no errors in ERA for a long time with an app using sdk 4.0.8. Recently i did an update, and used the latest SDK 4.1.4. The got a bunch of 'unexpected type error' - in an area i had done no changes. ERA gave the exact line number of the code.

While i could not debug i had to take guesses based on the the code line. I think the recent SDK have perhaps got some changes, regarding variable typing and perhaps detecting issues they did not detect before?

My code is older so does not take advantage of the newer strong variable typing.

Anyhow i added some code regarding type checking and it seems to be fixed now, no more errors in ERA.

_psx_ over 2 years ago in reply to OttawaDeveloper

Type checking is compiler feature not runtime.

I usually have problem with the newest device epix2/fenix7.

If the same code run well for most devices usually bugs means problem on particular device {e.g. full disk) or problem with vm.

It would be easier to do something if we have access to information about our user's device. For example if my app is used on 5 devices f7 and all of them have the same problem I can try to fix bug and report bug about problem with VM on f7.

But now only serious error on all device can be fixed and because I use my app it never happens

FlowState over 2 years ago in reply to Alan.raceQs

Alan.raceQs said:
All of the Fenix 6's were reporting running 22.10 Not sure how to find out current versions for Fenix 6. Best I can find is https://www8.garmin.com/support/download_details.jsp?id=15031 indicating 20.50. So what's that all about?

[https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series]

Alan.raceQs over 2 years ago in reply to BobMiles

OK, so it seems 22.10 is latest FW for F6, released around June 15. I don't capture the FW versions of my users, so can't draw any conclusions, but I have around 60 F6xxx users, but only this small number of crashes.

Dumb question: do all F6 variants (s, spro, xpro,..) use the same FW?

_psx_ over 2 years ago in reply to Alan.raceQs

It's difficult to say. Number of ver. is the same but for each device is prepared separated file (for beta/alpha).

flocsy🤠 over 2 years ago in reply to Alan.raceQs

How do you know the number of F6 users?

_psx_ over 2 years ago in reply to flocsy🤠

docs.google.com/.../edit

Alan.raceQs over 2 years ago in reply to flocsy🤠

Very early on, when starting to develop for mobile devices, I realised the importance, for support and development, of knowing what devices were being used, and how the app was being used on those devices, so from day 1 with my app on Garmin I implemented an HTTP-based monitoring system to capture statistics from each app start.