Charlie Niekirk

All I had to do to receive FCM messages from my app (or another app I suppose) was to call `register` with my `senderId` which is in `google-services.json`. This worked...

Thanks @mitsinsar, I thought you only had the issue with services? Also you version requires API 21, and I'm having to work with 19 :/

You can just use something like: `@Send void sendBinaryMessage(byte[] message);` in your interface and not use a message adapter.

I guess not then?

This may help, there is a login endpoint returned by the [https://api.musical.ly/rest/discover/navigate](url) : `/rest/passport/v2/login?___d=eyJhYyI6IlBPU1QiLCJieiI6InVzZXJfbG9naW4iLCJkbSI6IlVTRVIiLCJ2ZXIiOiJkZWZhdWx0In0%3D` 

@mangledbottles Yep I can confirm that the latest Android app for both Musically and Lively are not SSL pinned. I can use this packet capture app: [https://play.google.com/store/apps/details?id=app.greyshirts.sslcapture&hl=en](url) to capture all...

OK, I now know how the `X-Request-Sign5` header value is generated after quite a bit of trial and error and static analysis of the smali code from the Android APK....

Most likely is that your X-Request-Sign5 header value is invalid. The header value is an HMAC-SHA1 hash of the request info which contains a time stamp, if the time stamp...

Base64 decode your current X-Request-Info5 header value, replace the time stamp with a current one and then encode it with base64 again. Generate an HMAC-SHA1 hash of that new value...

It depends on whether or not you want to emulate the Android app or the IOS app.