-
Notifications
You must be signed in to change notification settings - Fork 10
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
Same user with multiple devices kicks out existing device #28
Comments
The code supports multiple devices just fine. |
I should probably add a little more detail. It supports multiple devices, but not when they only differ by device token. Here's an example: /var/lib/xaps/database.json with New_iPhone + iPad registered and working:
Starting the Old_iPhone:
/var/lib/xaps/database.json now (new iPhone is gone, old iPhone has replaced it because it has the same "Account" even though it has a different DeviceToken:
Note how the DB222D09-0BB8-4EE5-948C-9A1D7DCBA6CD account entry in the database has dropped the DeviceToken for New_iPhone and is now listing Old_iPhone. |
You could work around this by deleting the mail account on one device and recreate it. I see that this is a use-case, but it's a very narrow one. It would require database migration and a partial rewrite. If there is someone willing to sponsor the work or create a PR, give me a ping :) |
Agreed. Either way there's some risk in modifying the database structure, so perhaps it can simply be documented. I added this and a few other things to #29 |
I have several iOS devices. An old iPhone, a new iPhone (which started out life as a clone of the old one), and an iPad.
When I start mail, they all register. However, the old iPhone and new iPhone have the same AccountID, but different DeviceTokens. It looks like the code currently only supports one DeviceToken per AccountId. Whichever registers last wins.
Looks like the Account data structure and the Registration functions in database.go would have to be modified to support this?
The text was updated successfully, but these errors were encountered: