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

SDK Version 0.6.0 Example App Crashing #59

Closed
1 task done
zack-hable opened this issue Jun 18, 2018 · 4 comments
Closed
1 task done

SDK Version 0.6.0 Example App Crashing #59

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

Comments

@zack-hable
Copy link

zack-hable commented Jun 18, 2018

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.6.0

Android devices affected: Samsung Galaxy S8

Android OS version affected: Oreo 8.0.0

Beacon hardware version: G1.12

Description

After launching the example app and the scanner notification pops up the app crashes.

Expected behavior: Example app normal functionality (areas being shaded depending on if the phone is within the beacon)

Actual behavior: app crashes

Additional information

The app works fine/as expected on SDK version 0.5.0
log.txt

@pawelDylag
Copy link
Contributor

pawelDylag commented Jun 19, 2018

Hey @zack-hable

Stupid mistake, gonna be fixed soon :)
It only happens when you don't have proper tags associated to you beacons in Estimote Cloud.

Edit: The onError action is not reported on the main thread, so the default Toast message is causing the crash. You may fix this on your side, but we will also fix this in the SDK.

Thanks for reporting this!
Regards,
Paweł

@zack-hable
Copy link
Author

It seems to work as expected when all of the zones are setup correctly. Any ideas on #60 ?

@tzuviatwork
Copy link

We managed to workaround this problem.
Edit beacon settings through estimote cloud, so that the beacon has at least one attachment with value equal to tag.
If your code uses .forTag("tag") it works.
Indeed the error reporting callback needs not to trigger UI action. we changed it to just log.

@pawelDylag
Copy link
Contributor

Fixed in 0.6.1 :)

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

3 participants