"Could not update account information" when going afk in Sortie 1 and let the mission timer go 0 #1963

Closed
opened 2025-05-02 12:06:37 -07:00 by Animan8000 · 2 comments
Contributor

When going afk for too long, a timer will appear and if no enemy is getting killed within the time, the mission fails. On my end this seems to have triggered a "could not update account information".

2025-05-02T20:59:02:405 [0.1.0] http:   GET /api/credits.php?accountId=67d1c4cf77322d1aed16f26c&nonce=7443674826280757&ct=MSI 200 7.551 ms - 98
2025-05-02T20:59:14:268 [0.1.0] error:  SyntaxError: Unexpected non-whitespace character after JSON at position 18 (line 1 column 19) while processing /api/missionInventoryUpdate.php request
    at parse (<anonymous>)
    at JSONParse (D:\GitHub\spaceninjaserver\node_modules\json-with-bigint\json-with-bigint.cjs:80:10)
    at getJSONfromString (D:\GitHub\spaceninjaserver\src\helpers\stringHelpers.ts:5:21)
    at missionInventoryUpdateController (D:\GitHub\spaceninjaserver\src\controllers\api\missionInventoryUpdateController.ts:53:44)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-05-02T20:59:14:270 [0.1.0] http:   POST /api/missionInventoryUpdate.php?accountId=67d1c4cf77322d1aed16f26c&nonce=7443674826280757&ct=MSI&xpBasedLevelCapDisabled=1 500 4.395 ms - -
2025-05-02T20:59:17:646 [0.1.0] error:  SyntaxError: Unexpected non-whitespace character after JSON at position 18 (line 1 column 19) while processing /api/missionInventoryUpdate.php request
    at parse (<anonymous>)
    at JSONParse (D:\GitHub\spaceninjaserver\node_modules\json-with-bigint\json-with-bigint.cjs:80:10)
    at getJSONfromString (D:\GitHub\spaceninjaserver\src\helpers\stringHelpers.ts:5:21)
    at missionInventoryUpdateController (D:\GitHub\spaceninjaserver\src\controllers\api\missionInventoryUpdateController.ts:53:44)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
When going afk for too long, a timer will appear and if no enemy is getting killed within the time, the mission fails. On my end this seems to have triggered a "could not update account information". ``` 2025-05-02T20:59:02:405 [0.1.0] http: GET /api/credits.php?accountId=67d1c4cf77322d1aed16f26c&nonce=7443674826280757&ct=MSI 200 7.551 ms - 98 2025-05-02T20:59:14:268 [0.1.0] error: SyntaxError: Unexpected non-whitespace character after JSON at position 18 (line 1 column 19) while processing /api/missionInventoryUpdate.php request at parse (<anonymous>) at JSONParse (D:\GitHub\spaceninjaserver\node_modules\json-with-bigint\json-with-bigint.cjs:80:10) at getJSONfromString (D:\GitHub\spaceninjaserver\src\helpers\stringHelpers.ts:5:21) at missionInventoryUpdateController (D:\GitHub\spaceninjaserver\src\controllers\api\missionInventoryUpdateController.ts:53:44) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) 2025-05-02T20:59:14:270 [0.1.0] http: POST /api/missionInventoryUpdate.php?accountId=67d1c4cf77322d1aed16f26c&nonce=7443674826280757&ct=MSI&xpBasedLevelCapDisabled=1 500 4.395 ms - - 2025-05-02T20:59:17:646 [0.1.0] error: SyntaxError: Unexpected non-whitespace character after JSON at position 18 (line 1 column 19) while processing /api/missionInventoryUpdate.php request at parse (<anonymous>) at JSONParse (D:\GitHub\spaceninjaserver\node_modules\json-with-bigint\json-with-bigint.cjs:80:10) at getJSONfromString (D:\GitHub\spaceninjaserver\src\helpers\stringHelpers.ts:5:21) at missionInventoryUpdateController (D:\GitHub\spaceninjaserver\src\controllers\api\missionInventoryUpdateController.ts:53:44) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) ```
Sainan added the
bug
label 2025-05-02 15:07:10 -07:00
Owner

I am not even able to reproduce this mission failure. I just loaded the first mission (exterminate) and there does not seem to be a fail condition.

Could you please provide more accurate logs, like so?

image.png

I am not even able to reproduce this mission failure. I just loaded the first mission (exterminate) and there does not seem to be a fail condition. Could you please provide more accurate logs, like so? ![image.png](/attachments/e5bf148e-d755-45ba-8be5-6c872f1718f3)
Sainan added the
question
label 2025-05-02 15:16:41 -07:00
Author
Contributor

Closing as I cannot reproduce the issue anymore (idk why but whatever). Will re-open in case I can replicate it some day and have better logs.

Closing as I cannot reproduce the issue anymore (idk why but whatever). Will re-open in case I can replicate it some day and have better logs.
Sign in to join this conversation.
No description provided.