Closed MatthewGerber closed 6 years ago
I tried manually adding the EstimoteBluetoothScanning
framework to the bindings project, but then ran into the following issue:
https://github.com/Estimote/iOS-Proximity-SDK/issues/7
@heypiotr Can you please update these bindings to 0.12.0 to see if it fixes this issue?
Thanks!
@heypiotr Do you know when you might be able to get to this?
Done! Let me know if this worked for you.
@heypiotr Thanks for the updated bindings. They work perfectly on iOS. However, there seems to be a problem on Android. Your example Android app works fine when running the scanner in a foreground service. However, the foreground service does not work in any of my projects. I created a fresh Xamarin Android project and copy/pasted your example Android activity code into the project. I then referenced the Estimote bindings .dll, added the service declaration to the manifest, etc. Despite everything I have tried with this new Android project, I cannot get the Estimote bindings to run a BLE scan using a foreground service. The activity requests the location permission and calls observationHandler = observer.Start();
without any errors...then it just sits there without writing the usual messages to the console about BLE scanning, and proximity events are never reported.
I believe reproducing this should be simple: Just create a new Xamarin Android project, add your example activity code to it, and reference the Android bindings .dll. Can you get it to run the scanner in a foreground service?
I'm on a Mac, if it matters.
Please let me know what you think about this.
@heypiotr Another detail: If I do not run the scanner in a foreground service (i.e., by commenting out .WithScannerInForegroundService(notification)
) then everything works fine in my testing app -- I get the expected BLE scanner outputs in the console, and proximity events are detected.
So the issue is related to running the scan in a foreground service. This works in your example app, but does not work in any other app I have tried (my production app, my fresh Android app, etc.).
Any help would be greatly appreciated. Trying to push a release out...
@heypiotr just checking in on this. Have you tried reproducing the issue described above related to the foreground service?
This is still happening to me, is there a fix? I downloaded the proximity beacon xcode project and tried to run it, its not working with xcode 11 and swift 5.0 or swift 4.2
Hello -
I am trying to build the current bindings project. It does build, but running the iOS example app in the simulator crashes immediately with the following output:
Can you fix this on your end, or is it a problem on mine?
Thanks!