Errors from older version disappeared from ERA Viewer after uploading new version

I had 3 errors in the ERA Viewer about an hour ago. Then I published a newer version of the app, and now ERA Viewer is empty.

Is this normal?

Top Replies

jim_m_58 over 4 years ago in reply to dpawlyk +1

Seems to me, the only time viewing stuff for older releases would be useful is if you fail to address the issues with the current version before updating the store.

So just address all the issues in the…
sabeard over 4 years ago in reply to jim_m_58 +1

jim_m_58 said:
Seems to me, the only time viewing stuff for older releases would be useful is if you fail to address the issues with the current version before updating the store.

In which case, the errors…

All Replies

0 jim_m_58 over 4 years ago

Yes, 100% Normal. Before you send an update to the app store, you want to address everything you see in ERA for the current version.

0 flocsy🤠 over 4 years ago in reply to jim_m_58

What do you mean CURRENT version?

1. In the ERA Viewer there's an option to sort by "App Version", so it clearly knows that not only my current version can be bugs

2. Even if I fixed the errors in the current version, there will always be users who are on an earlier version.

3. How am I supposed to fix this error: https://forums.garmin.com/developer/connect-iq/i/bug-reports/system-error-on-genericchannel-getdeviceconfig-in-edge1030

4. Even if I fixed everything I knew of I would still like to be able to see them as before (I set the status to either read or fixed, but it shouldn't disappear)

0 jim_m_58 over 4 years ago in reply to flocsy🤠

Current version is the current version in the app store

It only knows the current version. Been that way since day one. When you send an update to the store, that becomes the current version. Sort by "App Version" only has that one version. There's no way to see ERA info for other versions of your app.

0 flocsy🤠 over 4 years ago in reply to jim_m_58

jim_m_58 either you are the best programmer I've ever heard of and you don't have any bugs in any of your apps, or you seem to be too used to a bad behaviour of ERA that is most probably a bug. If there wasn't the sort by App Version in there then I would think for 3 seconds that you are right, but since it's there I'm pretty sure that this is a bug.

0 jim_m_58 over 4 years ago in reply to flocsy🤠

It's called "experience". I first started publishing apps in 2015. long before ERA even existed. And yes, many of my apps are pretty bug free after all these years. When I do see something in ERA today, I address EVERTHING before updating the store. It's really that simple..

"App Version" in ERA likely isn't a bug as it works but there is only one version, and may be there for something in the future

0 flocsy🤠 over 4 years ago in reply to jim_m_58

That means you have to wait for a month before you can add a new feature (or add a new device) and release the next version, because otherwise you might not see some rare but existing bug?

The future is here :)

0 jim_m_58 over 4 years ago in reply to flocsy🤠

If there's an error, you'll normally see that in ERA right away. If it's rare, you'll see it in ERA with the new version.

I rarely update any app more than once every month or two. If you are getting a bunch of crashes, you should probably spend more time testing with a sideload or beta app.

0 dpawlyk over 4 years ago in reply to flocsy🤠

flocsy🤠 said:
That means you have to wait for a month before you can add a new feature (or add a new device) and release the next version, because otherwise you might not see some rare but existing bug?

No, you won’t miss any bug reports IF you look at ERA before uploading a new version.

For a new version, you’ll either have fixed the bug, or it will exist in old code in the new version (and be reported), or the bug will be in the new code (and be reported).

flocsy🤠 said:
Even if I fixed everything I knew of I would still like to be able to see them as before

Why?

0 dpawlyk over 4 years ago in reply to flocsy🤠

flocsy🤠 said:
Even if I fixed the errors in the current version, there will always be users who are on an earlier version.

There won’t be too many of them. They should be using the latest version anyway.

The only way you can fix bugs is by releasing a new version. So, you can’t help people who don’t upgrade. Knowing about bugs in prior versions is kinda useless.

0 peterdedecker over 4 years ago in reply to dpawlyk

dpawlyk said:
Knowing about bugs in prior versions is kinda useless.

I disagree, it would be very useful to have a view on the bugs of the previous version. In the case you want to determine when a regression occurs a full version history would be useful too.

Iirc in the first version of era there was actually full version history but in that version it was difficult to spot which errors were actually happening as of the release in the new version. So the current view is definitely an improvement in that area, but being able to switch to full history or previous version would have it uses as well.