Skip to content
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

use new enum encoding for client type #36

Merged
merged 3 commits into from
May 12, 2021
Merged

Conversation

owenpearson
Copy link
Member

resolved #34.

Unverified

This user has not yet uploaded their public signing key.
@KacperKluka
Copy link
Contributor

@owenpearson as I've written in the issue #34 merging this will break the compatibility with Android and iOS apps because those changes are not present there 😉 So I don't think that we should land this PR at the moment 😉

@QuintinWillison
Copy link
Contributor

@KacperKluka What should be the trigger to enable this PR to land?

@KacperKluka
Copy link
Contributor

KacperKluka commented Apr 29, 2021

@QuintinWillison Ideally both Android and iOS issues should be closed together with this JS issue. Otherwise, the mobile SDKs will crash show wrong asset statuses when a JS subscriber will be trying to subscribe for a trackable they are publishing.

@KacperKluka
Copy link
Contributor

Android PR is ready ably/ably-asset-tracking-android#310 so we can progress with this PR too 😁

Copy link
Contributor

@KacperKluka KacperKluka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 👍

@owenpearson owenpearson merged commit ecc79c7 into main May 12, 2021
@owenpearson owenpearson deleted the update-client-type-enum branch May 12, 2021 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Change names of client type values from presence data
3 participants