You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 29, 2022. It is now read-only.
Below is a conversation that I was having with my beacon provider regarding a new problem that has just occurred:
Rich Dabney4 Dec, 17:51 CET
Unable to deploy the update on the configured beacon.Deployed beacon t6YB to redirect to a clients haystack vcard.The redirect did not work so we removed it as a redirect and attempted to redirect the same beacon to a customer provided youtube video. we confirmed that the new urls are being redirected in near.place as intended, However, we are unable to access anything other than the previously failed haystack url redirect.
We configured and applied a new beacon so that we could confirm what the beacon in the field is now publishing 3huN tough beacon.
We entered the same near.place url and updated it in the web panel and the Kontakt.io Android app. applied the update and confirmed that it was written to and ready.
We are unable to detect this beacon as though we are being blocked.I went into the Kontakt Android app and logged out and then back in and confirmed all the settings were correct and they were, however, I am still stuck receiving the "Oops Contacts.thehaystackapp.com"
Please advise
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
Below is a conversation that I was having with my beacon provider regarding a new problem that has just occurred:
Rich Dabney4 Dec, 17:51 CET
Unable to deploy the update on the configured beacon.Deployed beacon t6YB to redirect to a clients haystack vcard.The redirect did not work so we removed it as a redirect and attempted to redirect the same beacon to a customer provided youtube video. we confirmed that the new urls are being redirected in near.place as intended, However, we are unable to access anything other than the previously failed haystack url redirect.
We configured and applied a new beacon so that we could confirm what the beacon in the field is now publishing 3huN tough beacon.
We entered the same near.place url and updated it in the web panel and the Kontakt.io Android app. applied the update and confirmed that it was written to and ready.
We are unable to detect this beacon as though we are being blocked.I went into the Kontakt Android app and logged out and then back in and confirmed all the settings were correct and they were, however, I am still stuck receiving the "Oops Contacts.thehaystackapp.com"
Please advise
The text was updated successfully, but these errors were encountered: