-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Push device registration omits clientId #877
Comments
@ricardopereira I'm able to reproduce this issue where we don't receive the Essentially in the example app's AppDelegate file. If you try and instantiate the library, but not connect to it (possibly by setting the So within
|
@Srushtika This makes sense. I've already a PR #874 which probably fixes that. Can you try that branch please? Remember, change the Podfile to |
#874 doesn't appear to fix it |
@tcard are you able to look at this please? @Srushtika can help you to reproduce it if necessary. |
@paddybyers I think you mean me right? 😄 I can see this in the afternoon. |
Below is an extract from a log. The issue we're seeing is that the Ably instance is being initialised with
ClientOptions.clientId = null
, but then later:it is given auth details with a
TokenRequest
that does contain aclientId
(see line 87 in the extract:ARTTokenRequest: keyName=lM4PsA.RZWvBw clientId=297455
)but still the push device registration created does not have a
clientId
. (We know that by decoding thedeviceIdentityToken
received, and also from backend logs.Can you think of a reason why the
LocalDevice.clientId
was not set?The text was updated successfully, but these errors were encountered: