I am using Nearby messages API for android. I was getting the attachments using API before, till end of January. However, it has abruptly stopped working. I can see the request calls my app making in the google cloud console. However, I am not getting any attachment. Is there anything that has been changed on the API end?
相关问题
- Google Nearby Connections 2.0 capabilities
- Nearby Connection 2.0: Identify endpoint over reco
- Multi peer connection using Google Nearby Connecti
- Google Nearby Messages - Cancel initial link betwe
- Google Proximity Beacon API: how to register iBeac
相关文章
- Multi peer connection using Google Nearby Connecti
- Google Nearby Messages - Cancel initial link betwe
- Google Proximity Beacon API: how to register iBeac
- 附近的优惠通知,当信标是无效(Nearby notifications when Beacon is
- 邻近连接2.0:混合不同的策略?(Nearby Connections 2.0: Mixing di
- Can't see my registered beacon in google beaco
- Not getting attachments from Nearby Messages API
- Nearby Connections 2.0: Advertiser restarts, but D
I work on the Nearby team. We've recently discovered and fixed a problem with the default message filter, which might be what's affecting you (e.g. if you don't provide a message filter at all). The fix is rolling out within the next day or two. Apologies!