The error is occurring in the file DeviceInformation.swift under Metaware/Core.

Xcode version: 11.2.1
Cocoapods version: 1.8.4

Let me know if you need any more information.

`[[[self.device.accelerometer.dataReadyEvent downloadLogAndStopLoggingAsync:YES progressHandler:^(float number) {

}] success:^(NSArray<MBLAccelerometerData *> * _Nonnull array) {
    
}] failure:^(NSError * _Nonnull error) {
    
}];`

The above code is giving the error "No visible @interface for 'BFTask<NSArray<MBLAccelerometerData *> *>' declares the selector 'success:'". Please suggest the correct method to use in Objective C

Hi,

The version 3 does not have any ANCS code. Are you planning to bring this functionality back?
The version develop2.0 has some code, but it does not work. It never finish the programming sequence when using the device.ancs object.

Best regards,

Clément

Good evening, we've changed to the new 3.0 SDK and the transmission of the sensor fusion data seems to be unstable. After a couple of seconds (or minutes, it's kind of random) the data stops transmitting to the mbl_mw_datasignal_subscribe method. Is there any other config we're missing? We've checked all the information provided by the documentation, both iOS and CPP. Thanks.

I am creating a CLI Application, that will run for MACOSX.
I want to connect to the MetaWear sensors to just log data to a file.

I am following the guide on here: https://mbientlab.com/iosdocs/latest/metawear_manager.html

If I instantiate a manager class, and attempt a connection alike this, I get a Thread dump stating:

Thread 1: EXC_BAD_ACCESS (code=1, address=0x0)

i.e The following line will cause a Thread dump above:

MBLMetaWearManager.shared();

My main class:

import Foundation

let runLoop = RunLoop.current;
let distantFuture = Date.distantFuture;

print("### we are in the create");
let starter = MetaWearStarter();
print("### we are after the create");

while (runLoop.run(mode: RunLoopMode.defaultRunLoopMode, before:    distantFuture)){
    print("### listening for a metawear device");
}

My MetaWearStarter class:

import Foundation

import MetaWear

class MetaWearStarter : NSObject {

    override init() {
        super.init();
        print("### we are in the init");
        startConnection();
    }

    func startConnection() {
        print("##### connection call was made");
        let manager = MBLMetaWearManager.shared();
        maanger.startScanForMetaWears() { array in
        print("### connection scan was complete")    
        // Hooray! We found a MetaWear board, so stop scanning for more
            MBLMetaWearManager.shared().stopScan()
            // Connect to the board we found
            if let device = array.first {
                device.connectAsync().success() { _ in
                    print("#### we connected to a device");
                    }.failure() { error in
                        print("### unable to connect");
                }
            }
        }
    }

}

I have a stack question opened here: https://stackoverflow.com/questions/46435965/metawear-cli-application-on-macosx

What exactly am I doing wrong in following the guide?

Hi,

i've updated to 2.8.3 and found this weird issue. I'm tracking MBLAccelerometerData and it is reported with the same timestamp. (everytime 3 events with different data in row has same timestamp, then another 3 events has same timestamp).

Version 2.8.2 works just fine.

Feel free to contact me for more info if needed

It would be great to have an option to build a static library with bitcode. The current framework is a dylib without bitcode; I'm not sure whether bitcode is possible in a dylib, but I was unable to get it to build with bitcode unless I switched to a static lib.

The C functions in MBLConstants.h can't be used from Objective-C++ code because when the header file is included by Objc-C++ code, it is assumed to have C++ linkage, but it is compiled with C linkage.

To fix this, the C functions could be declared like this:

#ifdef __cplusplus
extern "C"
#endif
NSString *MBLModelString(MBLModel model);

When using periodicSample(ofEvent:) to control the frequency of events, notifications are still sent event after successfully unsubscribing.

To replicate this, using the StarterProject, change DeviceViewController line 59 from:

device.accelerometer?.dataReadyEvent.startNotificationsAsync

to

device.accelerometer?.dataReadyEvent.periodicSample(ofEvent: 2000).startNotificationsAsync

Is there something that I should be doing differently to unsubscribe from notifications when using a filter?

Hello. I am developing an iOS application that will receive data from your device's gyroscope. For this, I use your SDK. While developing the application, I encountered an error. When I'm connected to a device via my app, my app crashes if anyone else connects to the device. XCode complains on board property of MetaWear class: EXC_ BAD_ACCESS. Could you give me any advice or fix this problem?