Server side call to async method returns Promise object, not value.

[robfallows]

Refer to this post on the Meteor forums and to @benjamn's comments which follow on.

In a nutshell, a Meteor.call done on the server does not get the return value of an async method. Instead, it gets the Promise object. This is at variance with the expected behaviour.

This has been observed since v1.3, but the reproduction uses v1.4.2.6:

Reproduction:

git clone https://github.com/robfallows/promise-issue promise-issue
cd promise-issue
meteor npm i
meteor

The server's console log shows the result of calling the async method (shows {} - expected "42"):

I20170214-11:23:14.415(0)? The answer to the ultimate question of life, the universe and everything is ... {}

The client browser shows the result of calling the async method from the client (shows "42" as expected):

The answer to the ultimate question of life, the universe and everything is ... 42

[philcruz]

I'm seeing this as well.

[Suppen]

As a workaround, I exported the method function and imported it where I was using it on the server (in another method), then used method.call(this) to get the correct context

[benjamn]

This issue should (finally!) be resolved if you run meteor update --release 1.4.3.3-beta.4 in your application directory, thanks to the commit 0cbd251 referenced above.

[robfallows]

Works like a charm - thank you @benjamn 👍