Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Physical web app crashes when beacon broadcasts two Eddystone URLs #918

Open
kirilraytchev opened this issue Jul 14, 2017 · 1 comment
Open

Comments

@kirilraytchev
Copy link

kirilraytchev commented Jul 14, 2017

Hi,
I'm pretty excited about the possibilities of Physical web and arranged a small test lab with:

  • iBKS plus beacon [https://accent-systems.com/product/ibks-plus/])
    • two of the 4 slots are configured as Eddystone URLs, broadcasting on 850 and 950 ms intervals
  • samsung galaxy prime
    • Android 5.0.2
    • Physical web app 0.2.1

What I notice is that Android Nearby app shows the two URLs, but the Physical Web app crashes with a Report message, disappearing after 2 seconds. This happens every time when I start the app and search for beacons.

screenshot_2017-07-12-18-28-58

@randelllamontgroup
Copy link

I also experience this issue when I'm broadcasting more than one (1) URL from a single beacon.
My environment is as follows:

  • Physical Web App Version: 0.2.1
  • Mobile Device Model: Samsung Galaxy S7 (SM-G930F)

The stack trace reveals a NullPointerException
stack_trace_20180114-011125

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

No branches or pull requests

1 participant