I am currently using digits for a web-application. I have been testing the application using my personal phone number, which works great. However, after asking my friend to try the app, he could not log in and received the error "Invalid phone number".
This error is very ambiguous. I tested entering his phone number using 3 different devices and different browsers, and the error was the same.
There is not much information that I could find about this error.
In addition to testing on my web-app, I asked him to try to sign into:
digits.com/signin, where he was also unable to log in and received the exact same error, "Invalid phone number". (The problem is not my application).
This error is especially strange since we have phone numbers from the same area code.
My Verizon number : +1 210 789 xxxx
Works fine
His T-Mobile number: +1 210 723 xxxx
Returns error
Any information on this would be helpful.
Thanks!
Related
I read here that EVM cards will sign some transaction data.
I would like to do this with my card, using my phone, and verify that the signature on the result is correct.
To start, I issued this command ("request APDU"):
00:A4:04:00:0E:32:50:41:59:2E:53:59:53:2E:44:44:46:30:31:00
One of the "Application IDs" was this:
A00000038410
So then I issued this command ("Select Payment application"):
00:A4:04:00:07:A0:00:00:00:03:10:10:00
and it returned this "Processing Options Data Object List (PDOL)":
9F66049F02069F37045F2A02
I read here how to decode this, because I couldn't find the official spec anywhere:
9F6604 - the tag 9f 66 represents the terminal transaction qualifiers
9F0206 - tag 9f 02 stands for authorized amount. The PDOL list must have the amount, authorized, coded into 6h bytes added to it.
9F3704 - tag 9f 37 stands for unpredictable number, thus encode such a number in 4 bytes and add it to the list
and here how to decode this:
5F2A02 - TX currency code
I understand the next step is to run "Get Processing Options" but this is where I got stuck. I tried:
80:A8:00:00:02:83:00:00
80:A8:00:00:12:83:10:01:02:03:04:05:06:07:08:01:02:03:04:05:06:07:08:00
80:A8:00:00:12:83:10:F3:20:40:00:00:00:00:01:00:00:04:04:06:03:05:08:00
80:A8:00:00:02:83:10:F3:20:40:00:00:00:00:01:00:00:04:04:06:03:05:08:00
All gave back a result of 6D:00 (Instruction code not programmed or invalid).
I tried looking in "emv book 3" and "emv book 4" but neither seem to contain the relevant information.
What do I need to do next in order to make a transaction, sign, and check the result?
Your GPO commands needs to provide the PDOL values requested by the card. The requested tags are:
9F66 - 4 bytes
9F02 - 6 bytes
9F37 - 4 bytes
5F2A - 2 bytes
So the commands needs to provide these in the same order, with expected lengths.
Assuming you want to send the following sample values:
9F66: 11223344
9F02: 112233445566
9F37: 11223344
5F2A: 1122
Your GPO command will look like this:
80A800001283101122334411223344556611223344112200
Where the PDOL data is 11223344112233445566112233441122.
Hope this helps
If PDOL found in response of select application, here you need to pass the value of PDOL tags in GPO command,
can find a very good article Here. hope it helps.
i've been trying to develop a project taht uses gps and cell location with SIM5320A, i have successfully implement the GPS location, but when i try to use the AT commands related to the Cell location the SIM responses with an error message, for that reason i bougth a FONA 3g to make some tests with the cell location, but im algo getting error messages.
Hope you can help me with that
thank you
`
at
OK
at+cpin=0000
OK
+STIN: 25
+STIN: 25
+CPIN: READY
a
SMS DONE
+VOICEMAIL: INIT_STATE, 0, 0
a
PB DONE
START
at+cassistloc?
ERROR
AT+ CASSISTLOCTRYTIMES=3,2
ERROR
`
UPDATE
I've seen in some forums taht some AT doesnt work depending on the firmware version, mine is 1575B12SIM5320A , should i update to the last one?
I am using square_connect ruby gem to refund payments.
body =
#<SquareConnect::CreateRefundRequest
#amount_money=#<SquareConnect::Money #amount=200, #currency="USD">,
#idempotency_key="be70cc12-28dd-4168-96ea-6eb78f299207",
#tender_id="asdkasdkakdakdakda">
All other parameters are just as intended. I have changed Tender key too.
result = api_instance.create_refund(authorization, location_id, transaction_id, body)
This gives me INTERNAL SERVER ERROR.
ETHON: performed EASY effective_url=https://connect.squareup.com/v2/locations/BP6GXQNEANA9B/transactions/b2fd4689-af1b-40a4-b706-aafd592e1111/refund response_code=500 return_code=ok total_time=1.883598
SquareConnect::ApiError: Internal Server Error - {"errors":[{"category":"API_ERROR","code":"INTERNAL_SERVER_ERROR","detail":"An internal error has occurred, and the API was unable to service your request."}]}
Are you sure that your tender_id matches a tender you want to refund? 500 isn't the correct response, but it seems like you are likely not selecting a correct tender to refund.
Also you should look into upgrading your SDK to the latest version.
This is a major bug in the Square Connect API. I was actually trying with a wrong transaction ID, instead of getting something like "Incorrect Transaction ID" I was getting 500 Internal Server Error.
I have been using Stripe, Payflow. Authorize.net, Braintree and Moneris API for almost 2 years now but I have never received a 500 Internal server error for a wrong transaction Id. So Square needs to address it on urgent basis.
I am using yowsup-cli, and it prints the following when I run "yowsup-cli version" ...
yowsup-cli v2.0.13
Using yowsup v2.4
I am trying to perform the registration as specified in the yowsup documentation, as follows. However, it fails.
First, I entered this command, and I indeed got a code back via SMS ...
yowsup-cli registration --requestcode sms --phone 1XXXXXXXXXX --cc 1 --mcc 310 --mnc 260
I then entered this command using the code I got back (shown as "AAA-BBB"), but it failed ...
yowsup-cli registration --register AAA-BBB --phone 1XXXXXXXXXX --cc 1
This is the error message I received ...
status: fail
reason: missing
What I did above is exactly what is described in the yowsup documentation, here: https://github.com/tgalal/yowsup/wiki/yowsup-cli-2.0#yowsup-cli-registration%29 (see the commands listed under "Example:").
Note that I get the same failure when I add the MNC and MCC info to the "--register" command.
Does anyone know why this registration procedure is failing, and what might be "missing" in what I'm doing?
Note that the MCC and MNC I specified are what I found when looking up my cell provider (T-Mobile, USA).
Also, note that I am able to run WhatsApp with no problems from my mobile device, as well as via their web interface.
Thanks for any help and suggestions.
you do not have to put "-" in your otp/code. it will be a plain sms code
yowsup-cli registration --register AAABBB --phone 1XXXXXXXXXX --cc 1
i hope it works
I am trying to open word Template from AX 2012 Reports. It works fine in the env I have developed but when I try to execute the same from different login I face the "COM error"
Please help.
You can always find help for these mysterious Office error codes by decoding the error code. COM error codes contain three major parts:
the top 4 bits indicate the severity of the error. 8 means "warning", one you can't ignore
the next 12 bits is the facility code, the origin of the error. 10 means "automation"
the lower 16 bits is the internal error code, the one that you really care about.
Switch your calculator to hex mode, 0x175d is error code 5981. Now turn to Google and query "word error 5981".
Lots of good hits, you can read them at your leisure. But clearly there's a problem with macros on that machine. Best left to the IT staff at your site, use superuser.com if you need more help with that.