Android: incompatible receiver, Map required!

[davidpricedev]

I'm getting the error "Incompatible receiver, Map required!" out of ./node_modules/twilio-sync/browser/subscriptions.js line 205

Relevant Versions:

"twilio": "^3.11.1"
"twilio-chat": "^2.1.0",
"twilio-common": "^0.1.7",
"react-native": "0.51.0",

and

13:08 $ yarn list | grep twilio
├─ twilio-chat@2.1.0
├─ twilio-common@0.1.7
├─ twilio-ems-client@0.2.6
├─ twilio-mcs-client@0.0.4
├─ twilio-notifications@0.4.4
├─ twilio-sync@0.7.4
├─ twilio-transport@0.1.4
├─ twilio@3.11.1

The stack trace in my app is:

• exports
• entries
• getIterator
• substract :: subscriptions.js:205
• getSubscriptionUpdateBatch :: subscriptions.js:235
• :: subscriptions.js:182
• emit
• backoff_

...

I'm fairly sure this is related to or caused by zloirock/core-js#368

Is there any way to work around this issue until it is resolved?

Notes:

• If there is a better place to report this, let me know.

[davidpricedev]

Working around the issue by setting the core-js versions back to 2.5.2 seems to have fixed the show-stopper, but introduced somewhat frequent occurrences of these errors during channel creation/deletion/join/leave:

ExceptionsManager.js:73 Chat E: Failed to get channel object Error: Unique name not found (status: 404, code: 54300)
at new SyncError (syncerror.js:34)
at mapTransportError (network.js:61)
at network.js:131
at run (es6.promise.js:66)
at es6.promise.js:79
at flush (_microtask.js:18)
at tryCallOne (core.js:37)
at core.js:123
at JSTimers.js:301
at _callTimer (JSTimers.js:154)
at _callImmediatesPass (JSTimers.js:202)
at Object.callImmediates (JSTimers.js:470)
at MessageQueue.__callImmediates (MessageQueue.js:275)
at MessageQueue.js:140
at MessageQueue.__guard (MessageQueue.js:262)
at MessageQueue.flushedQueue (MessageQueue.js:139)

Chat E: Failed to get roster object for channel <> Error: Map not found (status: 404, code: 54200)
at new SyncError (syncerror.js:34)
at mapTransportError (network.js:61)
at network.js:131
at run (es6.promise.js:66)
at es6.promise.js:79
at flush (_microtask.js:18)
at tryCallOne (core.js:37)
at core.js:123
at JSTimers.js:301
at _callTimer (JSTimers.js:154)
at _callImmediatesPass (JSTimers.js:202)
at Object.callImmediates (JSTimers.js:470)
at MessageQueue.__callImmediates (MessageQueue.js:275)
at MessageQueue.js:140
at MessageQueue.__guard (MessageQueue.js:262)
at MessageQueue.flushedQueue (MessageQueue.js:139)

Chat E: Failed to subscribe on channel objects <> Error: Map not found (status: 404, code: 54200)
at new SyncError (syncerror.js:34)
at mapTransportError (network.js:61)
at network.js:131
at run (es6.promise.js:66)
at es6.promise.js:79
at flush (_microtask.js:18)
at tryCallOne (core.js:37)
at core.js:123
at JSTimers.js:301
at _callTimer (JSTimers.js:154)
at _callImmediatesPass (JSTimers.js:202)
at Object.callImmediates (JSTimers.js:470)
at MessageQueue.__callImmediates (MessageQueue.js:275)
at MessageQueue.js:140
at MessageQueue.__guard (MessageQueue.js:262)
at MessageQueue.flushedQueue (MessageQueue.js:139)

Unhandled promise rejection Error: Map not found (status: 404, code: 54200)
at new SyncError (syncerror.js:34)
at mapTransportError (network.js:61)
at network.js:131
at run (es6.promise.js:66)
at es6.promise.js:79
at flush (_microtask.js:18)
at tryCallOne (core.js:37)
at core.js:123
at JSTimers.js:301
at _callTimer (JSTimers.js:154)
at _callImmediatesPass (JSTimers.js:202)
at Object.callImmediates (JSTimers.js:470)
at MessageQueue.__callImmediates (MessageQueue.js:275)
at MessageQueue.js:140
at MessageQueue.__guard (MessageQueue.js:262)
at MessageQueue.flushedQueue (MessageQueue.js:139)

Everything seems to work in spite of all these errors.

[aleksandrsivanovs]

Hi!

core-js is dependency of babel runtime, right?

the latter problem might be something on the edge between your use-case / our backend, so not necessarily package's problem. Can you, please verify that the problem persists on the freshly created service instance with no old channels and no old data?

[davidpricedev]

I can verify those issues (second set) are no longer present after starting with a newly created service instance.

[aleksandrsivanovs]

ok, so, it's inconsistent data on your (previous) service instance.
it seems that there was some blip in service.
basically - you can ignore those errors, as it won't expose any partial data to the client.
However, if you want us to check the "faulty" service instance - you can turn to our twilio support with your details (account sid and service sid) - we can check for inconsistencies and provide more specific info. (and it's not a good idea to share your account sid / instance sid ion github - hence asking to turn to twilio support :))

[aleksandrsivanovs]

can I close this issue now? :)

[davidpricedev]

certainly.

[prameetc]

Can you let me know how you exactly solved this? I am facing the same issue @davidpricedev, @aleksandrsivanovs . How should I add these dependencies?