RecordId was sent over the bridge, but it's not cached
See original GitHub issueRecordId was sent over the bridge, but it’s not cached. I am getting this error a lot when trying to implement WatermelonDB. It seems to be that I can make a query but once I make another query on the same table it gives me that error.
Diagnostic error: Record ID touchpoints#42fkr0mf4etavdw3 was sent over the bridge, but it's not cached
at diagnosticError (blob:http://localhost:8081/47ca6aff-f1b8-40cc-832a-52c832920571:136779:17)
at invariant (blob:http://localhost:8081/47ca6aff-f1b8-40cc-832a-52c832920571:136754:48)
at RecordCache._cachedModelForId (blob:http://localhost:8081/47ca6aff-f1b8-40cc-832a-52c832920571:138849:32)
at RecordCache.recordFromQueryResult (blob:http://localhost:8081/47ca6aff-f1b8-40cc-832a-52c832920571:138840:23)
at blob:http://localhost:8081/47ca6aff-f1b8-40cc-832a-52c832920571:138833:24
at Array.map (<anonymous>)
at RecordCache.recordsFromQueryResult (blob:http://localhost:8081/47ca6aff-f1b8-40cc-832a-52c832920571:138832:23)
at Collection._callee3$ (blob:http://localhost:8081/47ca6aff-f1b8-40cc-832a-52c832920571:137243:103)
at tryCatch (blob:http://localhost:8081/47ca6aff-f1b8-40cc-832a-52c832920571:27304:19)
at Generator.invoke [as _invoke] (blob:http://localhost:8081/47ca6aff-f1b8-40cc-832a-52c832920571:27479:24)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:9 (5 by maintainers)
Top Results From Across the Web
RecordId was sent over the bridge, but it's not cached in ...
While working on sync api implementation, data was not getting synced with the backend server. As I debug the issue using react-native ...
Read more >Scott Pritchard ( ified) on Twitter: "Cryptic errors like 'recordID was ...
Cryptic errors like 'recordID was sent over bridge but it's not cached'... like, OK? I just asked you to fetch some data. Not...
Read more >Record ID was sent over the bridge, but it's not cached
Record ID was sent over the bridge, but it's not cached. ... So, for all attention, I open this issue and copy it...
Read more >Changelog - WatermelonDB documentation - GitHub Pages
Fixed a possible cause for "Record ID xxx#yyy was sent over the bridge, but it's not cached" error; [LokiJS] Fixed an issue preventing...
Read more >lightning aura components - LWC Force Refresh Wire getRecord
... are not detected by Lightning Data Service. We're actively working on a feature whereby Lightning Data Service (and all of its @wire ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@arambrosius If you are using
react-native-navigationand passing a record throughpassPropsthen you will face this error.RNN creates a deep clone of
passPropsbefore passing them to the new screen and therefore destroys any reference to the original items. This causes problem with WDB if you pass in a record since the record has a reference to its collection and it has reference to its record cache asrecord.collection._cache. So when RNN clones this record, a newMapinstance is created for_cacheand this causes theRecordId was sent over the bridge, but it's not cachederror.An easy fix is to pass only the record id and let the receiver screen load the record.
@arambrosius no update. This is an open source project – I recommend that you put in some console.logs in the watermelon repo to try and track down why exactly the record was improperly cached.