How to cancel onBack

Hello,

Not sure if this is a bug and I haven't checked yet for other view types.

For ProgressBar, I pass a delegate that returns true on the onBack function, but when I press the back button, the view is poped from the stack.

I used the code provided on the docs: https://developer.garmin.com/connect-iq/

What am I missing?

PS: I tried on both simulator and real device.

Thank you!

Top Replies

Jan Čapek over 4 years ago in reply to flowstate +1

The real issue there is inability of CIQ team to determine whether something is feature or bug and actually DO something about it. You are correct, there are hundreds of similar "issues" across whole platform…
TomasSlavicek over 4 years ago in reply to myneur +1

When 21 people confirm that it does not work (in May 2021), and the ticket is still closed as "Cannot reproduce", that's something wrong.

Similar issue was with the broken OAuth login, or…
nielgaard over 3 years ago +1 suggested

It seems that in the base view of a widget, it does not matter what is returned by onBack(). The widget is always terminated when Back is invoked.

But if you push a new view with a behaviourDelegate, then…

All Replies

0 myneur over 4 years ago in reply to jim_m_58

Users report me the not working makeWebRequests continuously and one even submitted a requested log in https://forums.garmin.com/developer/connect-iq/i/bug-reports/makewebrequest-bad-request-on-some-devices. Garmin guys even know where's the problem. Yet nobody cares for over a year.

Similar story with the crashing simulator, wrong locations and other bugs. I gave up.

0 jim_m_58 over 4 years ago in reply to myneur

Sounds like the first one is a bug in GCM and not CIQ. This is an important thing to note when reporting bugs. CIQ doesn't determine priorities when other groups are responsible. They can't tell the GCM group when to fix things and in what order. That's set by the GCM group. So don't be too quick to blame it on CIQ (you can tell based on the ticket number who's bug it is)

Same with FW bugs. CIQ doesn't set other group's priorities or even when they release a FW update..

0 myneur over 4 years ago in reply to jim_m_58

The CIQ API does not work regardless if the bug is anywhere down the stream. I don't have information to triage that. I expect they are mature people in the same company who talk to each other. The error is manifested in the CIQ.
The GCM team does not solve bugs either. I reported before more than 2 years through the app that the GCM drains battery by stuck GPS after charging under some circumstances. No solution for years.

That's Garmin.

0 TomasSlavicek over 4 years ago in reply to myneur

When 21 people confirm that it does not work (in May 2021), and the ticket is still closed as "Cannot reproduce", that's something wrong.

Similar issue was with the broken OAuth login, or the "Navigation cannot be paused, when started from a Connect IQ app", this was also never fixed. I know some bugs are hard and multiple teams are involved, but at least these tickets should stay opened and should be actively researched.

0 nielgaard over 3 years ago

It seems that in the base view of a widget, it does not matter what is returned by onBack(). The widget is always terminated when Back is invoked.

But if you push a new view with a behaviourDelegate, then the delegate can catch the Back by returning true from onBack().