Push registration token refresh forces default ClientOptions
Originally, you had to pass a AblyRest instance when refreshing registration tokens, but now, the AblyRest is instanced by us, using the deviceIdentityToken as key, with default options. So, if the client relies on non-default options (custom fallbacks, custom push registration), token refresh won't work.
@paddybyers WDYT?
I agree this is a problem - I thought I'd already raised an issue for it somewhere.
Edit: I can't find it. The environment definitely needs to be persisted as part of the persisted LocalDevice details, together with anything else that is going to be needed if there's going to be a registration token update authenticated by deviceIdentityToken.