-
Notifications
You must be signed in to change notification settings - Fork 21
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
Improve migration experience #2186
Comments
How can we know that they are rare? I would approximate that every day averagely even more than ten of our iOS users switch to a new iOS device and if migration is still broken (we tried to fix it last year iirc), we should fix it again in near future. |
Proper solution for this would be sign out user when they restore from backup. |
@laurijamsa @markoaamunkajo I have done testing by backing up device to iCloud and restore it twice, I did not face the issue reported by the user. I see I am signed in fine and getting the data from cloud as expected. However, I have done some improvements in the code which may or may not caused this and I am expecting it will work as expected. Additionally, as mentioned above we could sign out users automatically when they restore from backup, should we do it? Its not very intuitive but it will probably prevent bugs like reported ones. Do we want to do it? |
We can keep users signed in after restoring the app from backups to a new device IF it finally works now. So we need to be able to test it in real life before making the decision. |
@markoaamunkajo You can probably download the app from firebase without REMOVING this app after restoring. That should give you same experience of downloading from AppStore. |
Finally tested this and when I open Ruuvi Station I am not signed in and no errors were shown. This is QA passed. |
Description:
User feedback, no screenshots. Looks like sign out did not happen properly for some reason for this user.
HI, migration of ruuvi app did not go smoothly when setting up new ipad from backup:
Migration issues are rare and low priority, keeping this in backlog for now. Solution for users at this point is to reinstall app.
The text was updated successfully, but these errors were encountered: