Aika FCM ta hanyar wakili ba ya bin hanyar haɗin wayar

Backend na iya aika buƙatar Firebase Cloud Messaging cikin nasara ta hanyar wakilin kamfani yayin da na'urar Android ba ta taɓa karɓar sanarwar ba. Buƙatar Admin API ta backend da haɗin FCM na na'urar hanyoyi ne daban.

Jagorar hanyar sadarwa ta Firebase ta ce ba za a iya ratsa ka'idar na'urar FCM ta hanyar wakilin cibiyar sadarwa ba. Sanya abokin ciniki na HTTP a wurin mai aikawa ba ya mai da wannan dindindin haɗin na'urar zuwa buƙatar wakilin HTTP.

Ga na'urorin Android, tashoshin TCP na manufa da aka rubuta su ne 5228, 5229, 5230 da 443. FCM yawanci yana amfani da 5228, sauran tashoshin kuma suna nan. Yi amfani da manufar da ta dace a cibiyar sadarwar da na'urorin da ke karɓa suke haɗawa.

Yi amfani da jagorar sunan mai masauki da Firebase ta buga lokacin da bangon wuta ya takaita wurare; tana hana lissafin barin IP da aka kayyade saboda adireshi na iya canzawa. Na'urori kuma suna buƙatar DNS mai aiki da tabbatacciyar hanya don haɗin su na dogon lokaci.

Idan mai aikawa ya gaza yayin samun token ko buƙatar Admin API, bincika wannan jigilar HTTP ta gefen uwar garke. Ga mu'amalar HTTP na Firebase Admin Java, saita jigilar API da jigilar shaidar tare. Idan aikawa ya yi nasara amma isarwa ta gaza, adana wannan sakamakon kuma bincika hanyar na'urar maimakon maye gurbin shaidar wakilin backend akai-akai.