Closed jaydenpung closed 4 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
should be fixed
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
should be fixed
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Pong
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
llaaaaaa
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
and again
@zabsalahid Reopen please
In modem.js, there is a call to modem.checkPINRequired where the error is not handled properly:
If there is an error, the 'result' will be
'{error: "ERROR", request: "checkPINRequired", status: "Error"}'
, where as the second parameter 'error' will be null. Checking for error and result.data.pinNeeded at the same time caused issue (calling pinNeeded on null).