Hi Morten, I never used the C SDK on Android. However, one of the common reasons for errors like this in C/C++ is related to the issues with the deployment of the "DAT" file containing the security-related information. You need to provide a valid CBOR-encoded file, and make sure it can be accessed as shown in the samples. Specifically in Android, the "file system" is restricted, so you need to make sure it gets placed in the areas accessible by your Android app.
Of course, I have no direct evidence, but that's the 1st thing to check with crashes like this (talking from experience of our team) Regards Max On Sun, Oct 29, 2017 at 2:01 AM, Morten Nielsen <m...@iter.dk> wrote: > Has anyone successfully used the C-SDK for Android? > > > > I’ve written a .NET Standard interop wrapper around the C-SDK and this > runs on Xamarin as well. I can successfully call ‘ > OCRegisterPersistentStorageHandler’ (confirming the interop works) but > when I call OCInit2, the app exits, without much of an error to go on (All > I get is “Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 6496”, > and I haven’t been able to get the native debugging to work yet) > > > > I’ve also enabled the same capabilities in the manifest as the Android > example apps have, so should be good there. > > > > Anyway just curious if anyone has actually ever gotten this to work before? > > > > > > Thanks > > /Morten > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev@lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > >
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
