Skip to content
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

Unable to create record once find has been called #42

Closed
mutewinter opened this issue Apr 12, 2014 · 4 comments
Closed

Unable to create record once find has been called #42

mutewinter opened this issue Apr 12, 2014 · 4 comments

Comments

@mutewinter
Copy link

Once store.find('type', id) has been called, store.createRecord(type, id) fails with the following error:

Error: Assertion Failed: The id ID has already been used with another record of type App.Type.

I believe this is because dematerializeRecord is never called on the store when the record is not found. Although it seems like the record should not be in the store until find succeeds.

@mutewinter mutewinter changed the title Unable to record record with ID once find has been called Unable to create record with ID once find has been called Apr 12, 2014
@mutewinter mutewinter changed the title Unable to create record with ID once find has been called Unable to create record once find has been called Apr 12, 2014
aputinski added a commit that referenced this issue Apr 12, 2014
Unfound records are now dematerialized.
@aputinski
Copy link
Collaborator

@mutewinter I think I fixed this, but I won't close it until I make the next release.

@ethanmuller
Copy link

I was experiencing the exact same issue. Building the latest version of master fixed things up for me. 👍

@oskarrough
Copy link
Contributor

I'm having the same issue now with Emberfire 1.2.6 and Firebase 1.1.1.

@dallasread
Copy link

I was having the same issue - solved it by this.store.unloadAll('message');

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

No branches or pull requests

5 participants