Delay in showing snippet about physical-web HOT 3 CLOSED

@matthewsibigtroth - I can help. Can you please elaborate on this bug a bit further? What is a snippet? Is a new sighting a new URL discovered via bluetooth?

I have been following the Physical Web project for a while. I have the code setup and running on Android Studio and can debug it on a Google Nexus 4. However, I do not have the hardware to broadcast an URL using BLE. Is the hardware setup a pre-requisite to fix this bug? If not, do you have ideas how we could otherwise simulate a new "sighting"?

I just got a RaspBerry Pi and will investigate ways to get it up and running to broadcast URL using BLE.

Thanks!

from physical-web.

The flow for information showing in the listview is as follows:

• when beacon is found If meta-data exists in hash-table then insert/update list view else request meta-data
• when meta-data request is complete update hash-table

so the initial insert into the listview is delayed by scan cycle -- a new beacon sighting is needed, whereas it could be inserted into the list view earlier.

this is a low priority bug. Lets find something that has more impact.

from physical-web.

@schilit Thanks for the details. I will keep exploring for other areas to contribute to. I need to get setup with a hardware anyway.

from physical-web.