Skip to content

Upgrade to matrix-android-sdk 0.9.14. #41

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

Merged
merged 1 commit into from
Feb 6, 2019
Merged

Upgrade to matrix-android-sdk 0.9.14. #41

merged 1 commit into from
Feb 6, 2019

Conversation

fancypantalons
Copy link
Contributor

There's a bunch of changes, required, to move to the latest SDK:

  1. Update AAR's. The matrix-sdk.aar in this commit was built from the
    v0.9.14 tag of the matrix-android-sdk git repository. olm-sdk.jar is
    pulled from the same place.

  2. Updates to the build scripts. matrix-android-sdk added kotlin as a
    dependency, moved to okhttp3, added io.realm, and so on.

  3. Code modifications to support new SDK itself. The changes, here, are
    a grab bag, and you're best off just reading the commit.

Of particular note, here, is that LoginRestClient.loginWithUser takes a
device name and a device ID, now (the previous API only took a device
name). As a wicked hack, right now, I'm just using the name as the ID,
but I have no doubt that's wrong and this should be cleaned up to
include a randomly generated, persisted device ID, as I believe this is
used by Synapse to track login sessions.

There's a bunch of changes, required, to move to the latest SDK:

1. Update AAR's.  The matrix-sdk.aar in this commit was built from the
v0.9.14 tag of the matrix-android-sdk git repository.  olm-sdk.jar is
pulled from the same place.

2. Updates to the build scripts.  matrix-android-sdk added kotlin as a
dependency, moved to okhttp3, added io.realm, and so on.

3. Code modifications to support new SDK itself.  The changes, here, are
a grab bag, and you're best off just reading the commit.

Of particular note, here, is that LoginRestClient.loginWithUser takes a
device name *and* a device ID, now (the previous API only took a device
name).  As a wicked had, right now, I'm just using the name as the ID,
but I have no doubt that's wrong and this should be cleaned up to
include a randomly generated, persisted device ID, as I believe this is
used by Synapse to track login sessions.
@tijder tijder merged commit 575f591 into tijder:master Feb 6, 2019
@tijder
Copy link
Owner

tijder commented Feb 6, 2019

Thanks for this merge request! Sorry it took so long to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants