Promise Error about africastalking-node.js HOT 7 CLOSED

The issue is that your number is not a string and in the format +2547xxxxxxx

@aksalj or @ianjuma :) need to fix the error message for when you have an invalid number format

from africastalking-node.js.

@denzelwamburu Ideally, it should not matter what framework you use. And any node version >= 0.12 should work fine.
Currently (v0.0.2), AfricasTalking.SMS.send() either thows an exception or always returns a promise; so this TypeError: Cannot read property 'then' of undefined should not occur.

from africastalking-node.js.

@aksalj i updated the library to version 0.0.2.
Works fine Now. :)

from africastalking-node.js.

This error (TypeError: Cannot read property then of undefined) should not occur even with the non-string to value because this is checking it and is supposed to throw an exception instead...

@pbombo yeah it should show a clear message instead of just throwing a generic error!

from africastalking-node.js.

@pbombo Even after using the format +2547xxxxxx, the error still persists

from africastalking-node.js.

@denzelwamburu what version of the library and node are you using?

Also when I replicate your code above like this

var AfricasTalking = require ('africastalking')({apiKey:null, username: null, format: "json"});
var sms = AfricasTalking.SMS;
var opts = {
    to: 0704654445,
    message: 'Server is Running'
};
console.log(opts);

sms.send(opts)
    .then(function(s) {
        console.log(s);
    })
    .catch(function(error) {
        console.log(error);
    });

here is what I (and should) get

TheWhiteRock:afticastalking aksalj$ node index.js 

/Users/aksalj/src/playground/afticastalking/node_modules/africastalking/lib/index.js:43
        throw error;
        ^
[object Object]
TheWhiteRock:afticastalking aksalj$ 

Like @pbombo said, opts.to needs to be a string like "254704654445" and not a number like 254704654445.

from africastalking-node.js.

Hey @aksalj am on node v5.4.1 and library v0.0.1
Still using that string format throws the same error.
Apparently am using loopback, but when using express v4.13.1 throws the error you are getting.
Could it be the node version? Or the loopback library? or Both ? 😣
Saw an issue with node version here #12

from africastalking-node.js.