Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proximity Notification Trigger Not Working #60

Open
1 task done
zack-hable opened this issue Jun 18, 2018 · 7 comments
Open
1 task done

Proximity Notification Trigger Not Working #60

zack-hable opened this issue Jun 18, 2018 · 7 comments
Assignees

Comments

@zack-hable
Copy link

Prerequisites

  • Put an X between the brackets on this line if you have done all of the following:
    • My beacons have Estimote Monitoring enabled (Check it in the Estimote Cloud, or via app)
    • My Android device/devices supports BLE and has Android OS version >= 5.0.0
    • My Android device/devices have bluetooth enabled
    • My app has Location Permissions granted

Basic information

Estimote SDK version: 0.5.0

Android devices affected: Samsung Galaxy S8

Android OS version affected: Oreo 8.0.0

Beacon hardware version: G1.12

Description

Using the example app on SDK version 0.5.0 and trying to use the Proximity trigger results in no notification being shown

(Optional) Steps to reproduce:

  1. Leave all beacons facing down (off)
  2. Start example app
  3. Enable trigger in example app
  4. Close example app (still visible/running in taskbar)
  5. Flip over/turn on beacons
  6. No notification is shown (waited a couple minutes)
  7. Open app from task menu and see beacons detected

Expected behavior: A notification to be shown

Actual behavior: No notification shown

Additional information

log.txt

@RasoolMohamed27
Copy link

Please provide update on this issue.

@RasoolMohamed27
Copy link

Our App is on Playstore. Please fix this issue.

@pawelDylag
Copy link
Contributor

Hello,

Proximity Trigger is still a beta feature, I'm sorry if it was not properly announced. You can always write your own scanning service implementation using this:

    fun triggerPendingIntentWhenInProximity(pendingIntent: PendingIntent)

Remember to implement your own PendingIntent - you can start the ProximityObserver in a custom BroadcastReceiver for example.

We're working on improving this feature, and we've added more improvements to our backlog :)

@RasoolMohamed27
Copy link

Hi,

Thank you for your reply. Implemented and testing as you advised and will update to you soon.

App is crashing all the time after updated to new version '1.0.3'. Please find the error screenshots below and please do the needful.

Screenshot : 1

image

Screenshot : 2

image

@zack-hable
Copy link
Author

What I ended up doing was integrating the AltBeacon Library into my app and that seems to support pretty much every android OS. You can find my implementation with Estimote Libs and AltBeacon here: https://github.com/zack-hable/estimote-cordova/tree/master/src/android

@RasoolMohamed27
Copy link

Hi zack-hable,
I can see old version of Proximity SDK used in your link. Also I need help in Background Trigger not in Foreground. Please let me know if you have any update on Background Proximity Trigger using latest version of Proximity SDK.

Hi pawelDylag,
Any update on above attached crashes in '1.0.3'. Its happening all the time when opening the app and unable to test it due to that. Please reply.

@rasoolmohamed
Copy link

Hi pawelDylag,
Please provide update on above issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants