Skip to content

Handle duplicate android device tokens correctly #673

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 4 commits into from
Feb 29, 2016
Merged

Handle duplicate android device tokens correctly #673

merged 4 commits into from
Feb 29, 2016

Conversation

stephentuso
Copy link
Contributor

Fixes #672 by treating an installation queried by objectId the same way as a matched installationId.

@gfosco
Copy link
Contributor

gfosco commented Feb 26, 2016

This fails 2 existing tests which cover installation duplication... See ParseInstallation.spec.js. It might be a good place to start to create a test there which covers your scenario.

@facebook-github-bot
Copy link

@stephentuso updated the pull request.

@facebook-github-bot
Copy link

@stephentuso updated the pull request.

@stephentuso stephentuso changed the title Possible quick fix for #672 Handle duplicate android deviceokens correctly Feb 27, 2016
@stephentuso stephentuso changed the title Handle duplicate android deviceokens correctly Handle duplicate android device tokens correctly Feb 27, 2016
@gfosco
Copy link
Contributor

gfosco commented Feb 29, 2016

Looks good to me... 👍

gfosco added a commit that referenced this pull request Feb 29, 2016
Handle duplicate android device tokens correctly
@gfosco gfosco merged commit 04491fc into parse-community:master Feb 29, 2016
@stephentuso stephentuso deleted the installation-handling-fix branch March 1, 2016 23:02
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.

3 participants