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

Eddystone beacon not showing Nearby notification #948

Open
msoftware opened this Issue Oct 7, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@msoftware

msoftware commented Oct 7, 2018

After configuring a eddystone beacon I can see the "unregistered" Eddystone-URL in the Android "Beacon Tool" but not as "nearby notification".
I found the following lines in the logcat of my device:
2018-10-07 13:08:34.391 530-18111/? D/vendor.qti.bluetooth@1.0-wake_lock: Acquire wakelock is acquired 2018-10-07 13:08:34.391 530-18111/? I/vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK 2018-10-07 13:08:34.434 530-18111/? I/vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE 2018-10-07 13:08:34.434 530-18111/? I/vendor.qti.bluetooth@1.0-ibs_handler: SerialClockVote: vote for UART CLK OFF 2018-10-07 13:08:34.434 530-18111/? E/vendor.qti.bluetooth@1.0-wake_lock: Release wakelock is released 2018-10-07 13:08:34.435 9795-20141/? W/NearbyDiscovery: Disabled by server: https://ux5.de/game, https://play.google.com/store/apps/details?id=com.jentsch.smartsquares, URL invalid: https://play.google.com/store/apps/details?id=com.jentsch.smartsquares [CONTEXT service_id=49 ] 2018-10-07 13:08:34.437 9795-7285/? I/BeaconBle: Client requested scan, settings=BleSettings [scanMode=ZERO_POWER, callbackType=ALL_MATCHES, reportDelayMillis=0, 6 filters, 1 clients, callingClientName=Nearby] 2018-10-07 13:08:34.457 9795-7285/? I/BeaconBle: Stopping scan on delegate scanner. BT state: 12 2018-10-07 13:08:34.458 9795-7285/? D/BluetoothAdapter: isLeEnabled(): ON

I changed the URL and the ID if the beacon but it does not work. During my tests I figured out, there are request comming from the physical Web crawler:

`Every 2.0s: grep PhysicalWeb /var/log/apache2/ux5.de.access.log Ubuntu-1804-bionic-64-minimal: Sun Oct 7 13:42:42 2018

66.249.69.118 - - [07/Oct/2018:12:10:02 +0200] "GET /app HTTP/1.1" 301 2631 "-" "Mozilla/5.0 (Google-PhysicalWeb)"
66.249.69.116 - - [07/Oct/2018:12:18:39 +0200] "GET /app HTTP/1.1" 301 2631 "-" "Mozilla/5.0 (Google-PhysicalWeb)"
66.249.81.178 - - [07/Oct/2018:13:02:02 +0200] "GET /game HTTP/1.1" 301 2631 "-" "Mozilla/5.0 (Google-PhysicalWeb)"
66.249.69.116 - - [07/Oct/2018:13:07:53 +0200] "GET /game HTTP/1.1" 301 2631 "-" "Mozilla/5.0 (Google-PhysicalWeb)"
66.249.69.116 - - [07/Oct/2018:13:13:04 +0200] "GET /game HTTP/1.1" 301 2631 "-" "Mozilla/5.0 (Google-PhysicalWeb)"
66.249.69.114 - - [07/Oct/2018:13:13:04 +0200] "GET /app HTTP/1.1" 200 4803 "-" "Mozilla/5.0 (Google-PhysicalWeb)"
66.249.69.118 - - [07/Oct/2018:13:19:03 +0200] "GET /game HTTP/1.1" 301 2631 "-" "Mozilla/5.0 (Google-PhysicalWeb)"
66.249.69.118 - - [07/Oct/2018:13:25:11 +0200] "GET /game HTTP/1.1" 301 2631 "-" "Mozilla/5.0 (Google-PhysicalWeb)"
66.249.69.116 - - [07/Oct/2018:13:30:58 +0200] "GET /game HTTP/1.1" 301 2631 "-" "Mozilla/5.0 (Google-PhysicalWeb)"
66.249.69.114 - - [07/Oct/2018:13:36:02 +0200] "GET /game HTTP/1.1" 301 2631 "-" "Mozilla/5.0 (Google-PhysicalWeb)"`

My question is, why does the NearbyDiscovery repeats the message "Disabled by server https://ux5.de/game, https://play.google.com/store/apps/details?id=com.jentsch.smartsquares, URL invalid: https://play.google.com/store/apps/details?id=com.jentsch.smartsquares [CONTEXT service_id=49 ]"?

@Zimbu98

This comment has been minimized.

Show comment
Hide comment
@Zimbu98

Zimbu98 commented Oct 7, 2018

Links to the Google Play store are not supported:
https://developers.google.com/nearby/notifications/developer_faq

@msoftware

This comment has been minimized.

Show comment
Hide comment
@msoftware

msoftware Oct 7, 2018

Thank you for the support.

msoftware commented Oct 7, 2018

Thank you for the support.

@Zimbu98

This comment has been minimized.

Show comment
Hide comment
@Zimbu98

Zimbu98 Oct 7, 2018

Forgot to mention, you can send people to the app store using Eddystone UID rather than Eddystone URL. You need an Eddystone UID beacon, be sure to configure it with a unique ID numbers, then setup Google Beacon Dashboard account within Google's developer platform. It's a little tricky to figure out how to set it up the first time, but reasonably easy to handle once it is up and running.

Zimbu98 commented Oct 7, 2018

Forgot to mention, you can send people to the app store using Eddystone UID rather than Eddystone URL. You need an Eddystone UID beacon, be sure to configure it with a unique ID numbers, then setup Google Beacon Dashboard account within Google's developer platform. It's a little tricky to figure out how to set it up the first time, but reasonably easy to handle once it is up and running.

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