Is this a known thing that I can ignore? Circular dependency error that makes no sense.

Hi,

I have a single, lone ERA report saying "Error Name: Circular Dependency Error" triggered by a method call in onExitSleep of a watch face which... sounds bad... but I have reviewed the code in question and there is literally no way that it _can_ be a circular error... And, if there was, I would expect to have seen a deluge of similar errors as I'm pretty sure that onExitSleep will be called more than once in the weeks since the last update.

Is this likely a Garmin bug or should I dig a little deeper?

0 9635560 over 3 years ago in reply to jim_m_58

The ERA report is a Captain America which, I'm pretty sure, is CIQ3 still.

0 jim_m_58 over 3 years ago in reply to 9635560

Yes, only the venu2 and venu2s are running CIQ 4.x

0 9635560 over 3 years ago in reply to jim_m_58

Ok, I have another and probably more compelling reason not to make it a weak reference...

If I have a weak reference to the BufferedBitmap, then it is instaneously cleaned up out of memory as the only thing that referred to it was my class, so having a weak reference gives it a reference count of zero. :(

0 jim_m_58 over 3 years ago in reply to 9635560

Using the memory viewer in the sim you might be able to tack down the circular reference.

0 9635560 over 3 years ago in reply to jim_m_58

Nothing obvious.

Besides, I only know of the potential circular reference via the ERA report. As I say, nothing logically _can_ be a circular reference.

Outside of the view and app classes, there are only two objects defined... one is a BufferedBitmap, the other is an object declared once, at view startup, with absolutely no references to it or from it outside of the one needed to allow the app to find it.

ETA: Every other thing in my view class is either a string or a number or a boolean.