Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SyncUser.getRefreshToken() is package-local, shouldn't it be public?

See original GitHub issue

Goal

What do you want to achieve?

Expected Results

Successful login and synchronization

Actual Results

Cannot login with previous token since SyncUser does not expose getRefreshToken() anymore.

I managed to find some code that uses reflection to access this method, but I don’t believe this should be the way.

Steps code to reproduce

SyncCredentials creds = SyncCredentials.usernamePassword("xxxxxxxxxx", "xxxxxxxxxxx");

SyncUser.Callback callback = new SyncUser.Callback<SyncUser>() {
    @Override
    public void onSuccess(SyncUser user) {
        SyncConfiguration build = new SyncConfiguration.Builder(user, REALM_URL)
                .waitForInitialRemoteData()
                .modules(new CnaRealmModule())
                .build();
        Realm.setDefaultConfiguration(build);

        Token refreshToken = getRefreshToken(user);

//      prefs.realmRefreshToken()

    }

    public void onError(ObjectServerError error) {
        String errorMsg;
        switch (error.getErrorCode()) {
            case UNKNOWN_ACCOUNT:
                errorMsg = "Account does not exists.";
                break;
            case INVALID_CREDENTIALS:
                errorMsg = "User name and password does not match";
                break;
            default:
                errorMsg = error.toString();
        }
        Log.d(TAG, errorMsg);
        Toast.makeText(LoginActivity.this, errorMsg, Toast.LENGTH_SHORT).show();
    }
};
SyncUser.loginAsync(creds, REALM_AUTH_URL, callback);