Error: Symbol Not Found Error / initialize() at Rez:54

jim_m_58 said:

You can check a specific device here: https://developer.garmin.com/connect-iq/compatible-devices/

Or:

1. Download the same info parsed into a spreadsheet here: https://forums.garmin.com/developer/connect-iq/f/discussion/231046/current-sdk-and-compatible-devices-parsed-into-a-searchable-excel-spreadsheet-for-those-who-value-such-things

2. Filter the "additionalFeatures" column in the "Compatible_Devices_3_1_9.json" tab for records containing "hasBleCentralClient"

Other BLE properties:

Here's what I do in getInitialView() for my BleScan app to handle this (I display a message if there's no support.)

I do it here as the boolean I use is in the view, and also, I pass the view to other things .  In this case, there is no profile manager

    function getInitialView() {
        var view=new BleScanView();
        if(Toybox has :BluetoothLowEnergy) {
        	view.hasBle=true; 	
			Ble.setDelegate(new BleScanBleDelegate(view));
			Ble.setScanState(Ble.SCAN_STATE_SCANNING);
		}		   	   
        return [view,new BleScanDelegate(view)];
    }

You're kind of mixing a few things together here.  There's the ble to talk to a phone, and then there's what I call CIQ BLE to talk to a sensor using low level BLE.  Two really different things.

It's like using a sensor that's ANT and paired to a device, or using ANT calls to talk directly to something (like an unsupported sensor).

Hi Jim,

I understand what you are saying; but in the manifest I select min API version 3.1.8.
Then build targets give one a choice of devices; many being grayed out to say they don't support API level.

I now understand that supporting that API level does not mean all features of the project are supported; at the moment this BLE and location; but then how do I know which devices support the features I need. Is this specified anywhere.

Is this not the tick list specified in the manifest also; so I say i need BLE and Location.

Then surely the device list only highlights the devices that support BLE and Location; all others grayed out.

So is there a bug in build system that says Vivoactive 3, forerunner 935 is supported; but in reality they are not supported.
Hence your test you highlight to check if the device does actually support the feature.

How can I tell which devices really do support the features I need? I can't run out and buy the whole garmin product range.

If it is a build system bug; hopefully Garmin will fix.

Many thanks,
Owain

Not really.  You'll find a whole bunch of things that are at the same SDK level, based on the device, and some things are available and somethings aren't.

And there are cases where an app can use something if it's available, but if it's not, can still run, so you really can't block something based on a permission.  A great example is background services in apps.  There's really no reason to block building something because the background permission is set and backgrounding is not available.  In my weather widjets, what happens is if there's no backgrounding, it makes the request in the main app..

Another example is SensorHistory.  Devices at the same CIQ can support it or not.  for wearables, getHeartRateHistory if there OHR, and the other get***History, only if there's a baro altimeter.

That's where "has" can be handy.

Hi Jim,

I just tried Vivoactive 3 music; and it just worked as you said.

Super; but on the device support front kind of need a clear map of support.

Owain

Actually, all you got to do is set the targets that have the functionality you need.  Have a va3m target but not a va3.  A 945 but not a 935 (it doesn't support CIQ BLE either)

A rough roadmap is, if the device came out before the f5+, no BLE.  For newer devices, all that support 3.1 (so while the fr45 and Swim2 are newer, they are running CIQ 1.4)

And there are a few exceptions, like the 645 music does, the 645 non-music doesn't