Approach S62: "Native base view is not supported." error

My widget performs the following:

From a view: WatchUi.pushView(new WatchUi.ProgressBar(...), ...)
From the ProgressBar: WatchUi.switchToView(new WatchUi.Menu2(...), ...)

This fails specifically on the Approach S62 device with the following error:

Error: System Error
Details: Native base view is not supported.
Stack:
- switchToView() at T:\mbsimulator\submodules\technology\monkeybrains\virtual-machine\api\WatchUi.mb:3813 0x3000357c
- presentMenu() at [call site of the WatchUi.switchToView]

I've observed this happening generally if you don't maintain at least one view in the stack, but as said, this fails specifically on the Approach S62.

Any ideas?

Top Replies

Travis.ConnectIQ over 4 years ago +1
If you look at the release notes (in ${SDK_ROOT}/README.html) under the v3.1.0beta1 section there are entries that read:
- Allow native UI pages to be set as the initial view.
- Allow switchToView() to work…

All Replies

jim_m_58 over 4 years ago

What type of app? The S62 is on CIQ 3.0. Are the other devices you're trying on CIQ 3.1?

Travis.ConnectIQ over 4 years ago

If you look at the release notes (in ${SDK_ROOT}/README.html) under the v3.1.0beta1 section there are entries that read:

Allow native UI pages to be set as the initial view.
Allow switchToView() to work between native pages, and from non-native to native pages.

The ProgressBar is a native view, and you're calling WatchUi.switchToView(). This is expected to work with devices that have support for ConnectIQ 3.1.0 or later, and it will fail for devices without that support.

I'm guessing that the simulator does not generate an error for this case. I'm not sure exactly how difficult it would be to do that, but it definitely would be nice.

zmullett over 4 years ago in reply to jim_m_58

It's a widget, targeted to min SDK 3.0.x. Which other devices are guaranteed to be on 3.0?

jim_m_58 over 4 years ago in reply to zmullett

As far as WW devices, not many, but there could be some APAC variants. You can look in bin/devices.xml or check by running something in the sim. You could set min SDK to 3.1 for the project (in the manifest.

zmullett over 4 years ago in reply to jim_m_58

Somehow my Forerunner 945 that I bought last year in Switzerland is considered an APAC variant - I'm unable to find my own widgets in the Connect IQ store if I publish them as min SDK 3.1. This is partially why I'm keen to stick to 3.0, unless that can be resolved by Garmin somehow (I assume there are others in the same situation).

jim_m_58 over 4 years ago in reply to zmullett

Check "about" on the watch and see what version of CIQ it has.

Former Member over 4 years ago in reply to jim_m_58

The CIQ version on my S62 is 3.0.12 if that helps?

jim_m_58 over 4 years ago in reply to zmullett

Are you sure you are up to date with the FW on the 945? What I see in devices.xml in the 3.1.9 SDK is both the ROW and APAC variants have CIQ 3.1

zmullett over 4 years ago in reply to jim_m_58

My 945 reports SDK version 3.1.7. Recently I performed some update although I'm not sure if it was a system update or just some maps. That said, I would like my widget to be able to support 3.0.x devices if possible.

jim_m_58 over 4 years ago in reply to zmullett

But this also means that with a min of CIQ of 3.1, you can support your 935.

I really doubt this functional will be backported from 3.1 to 3.0, so you may want to hope that the S62 moves to 3.1 fairly soon.