B4X FEED FCM - Migrate from legacy HTTP to HTTP v1 - how to get access token for client to client messsaging?

اطلاعات موضوع

درباره موضوع در تاریخ, در دسته b4xfeed ایجاد شده و آغاز کننده آن practicalsoftمی باشد و موضوع آن: FCM - Migrate from legacy HTTP to HTTP v1 - how to get access token for client to client messsaging? است. این موضوع تا کنون 26 بازدید کننده و, 0 پاسخ داشته و 0 بار پسندیده شده...
نام دسته b4xfeed
نام موضوع FCM - Migrate from legacy HTTP to HTTP v1 - how to get access token for client to client messsaging?
آغاز کننده موضوع practicalsoft
تاریخ شروع
پاسخ‌ها
0
بازدیدها
26
پسندها
0
آخرین ارسال توسط PracticalSoft
Jun 6, 2020
11,559
4,422
I've just uploaded my app to Play Store with a new feature which involves sending FCM notifications from one device to other devices which also have the app. Basically one device reads information from a web server and then tells the other devices so they don't have to bother the server.

I've adapted the legacy HTTP version described here - but placing the sending code inside my app. It works as intended.

However, PlayStore gives an error "Your app contains exposed Firebase Cloud Messaging (FCM) server keys." and gives a deadline of 21 January next year to update to the HTTP V1 API for FCM.

OK, so I've started out using Oauth2 to get the required access tokens, with scope = " " - but now when my app attempts to get a token it opens a browser window to have the user enter an email address to log in to Google... which is not good. and now I'm...



 

عقب
بالا