"Match error: Expected string, got object"

[JohnAllen]

We got the error above with the stack trace in the image.

The code is essentially structured to the code in issue #9.

This only happens using node-inspector BTW.

Any thoughts?

[vsivsi]

This sounds like an _id type issue.

Until now, jobCollection has required Mongo style IDs, which manifest in Meteor as type Meteor.Collection.ObjectID (an EJSON custom type). If you are specifying String type Ids for Job documents, then it currently won't work and you'll get this error.

Another issue (#12) requested a relaxation of this requirement, to allow use of random strings for Ids as well. I've implemented that, and it got merged into the master branch yesterday, but I haven't published it to Atmosphere yet (I will tonight).

So check to see if you are setting any Job _id values to a String... If that's it, then the code I'm releasing tonight should fix it for you. As a part of that, the default auto-generated _id type will be changing from Mongo-style to random string. This behavior can be controlled by setting the idGeneration option when you create your JobCollection.

If you think your problem has nothing to do with Ids, then give me a shout back, but it seems about 90% likely that this is your issue.

[vsivsi]

I've published v0.0.14 to Atmosphere which permits using String type _id values. Please let me know if this solves your issue.

[vsivsi]

Resolved long ago. Closing.