Ongeki unhandled v140 request GetUserMemoryChapterApi #137

Closed
opened 2024-05-08 07:24:48 +00:00 by Kayori · 8 comments
Contributor

First card scan works but then after trying it again the second time i get this error in artemis

[2024-05-07 21:05:42] Ongeki | INFO | v140 GetUserMemoryChapterApi request from 192.168.192.115
[2024-05-07 21:05:42] Ongeki | DEBUG | {'nonce_': -125590606, 'userId': 10000}
[2024-05-07 21:05:42] Ongeki | WARNING | Unhandled v140 request GetUserMemoryChapterApi
[2024-05-07 21:05:43] Ongeki | INFO | v140 GameLogoutApi request from 192.168.192.115
[2024-05-07 21:05:43] Ongeki | DEBUG | {'nonce_': -1973021118, 'userId': 10000}
[2024-05-07 21:05:43] Ongeki | DEBUG | Response {'returnCode': 1, 'apiName': 'gameLogout'}

First card scan works but then after trying it again the second time i get this error in artemis [2024-05-07 21:05:42] Ongeki | INFO | v140 GetUserMemoryChapterApi request from 192.168.192.115 [2024-05-07 21:05:42] Ongeki | DEBUG | {'nonce_': -125590606, 'userId': 10000} [2024-05-07 21:05:42] Ongeki | WARNING | Unhandled v140 request GetUserMemoryChapterApi [2024-05-07 21:05:43] Ongeki | INFO | v140 GameLogoutApi request from 192.168.192.115 [2024-05-07 21:05:43] Ongeki | DEBUG | {'nonce_': -1973021118, 'userId': 10000} [2024-05-07 21:05:43] Ongeki | DEBUG | Response {'returnCode': 1, 'apiName': 'gameLogout'}
Collaborator

May we know if you are on the master or develop branch?

1.40 is not supported on master

May we know if you are on the master or develop branch? 1.40 is not supported on master
Author
Contributor

I'm on latetst develop just checked

On branch develop
Your branch is up to date with 'origin/develop'.

I'm on latetst develop just checked On branch develop Your branch is up to date with 'origin/develop'.
Collaborator

I can't seem to be able to replicate this issue on my end, this request is already part of brightmemory.py and the defines seems all good

I can't seem to be able to replicate this issue on my end, this request is already part of brightmemory.py and the defines seems all good
Author
Contributor

I'll try completely reinstalling then importing again

I'll try completely reinstalling then importing again
Author
Contributor

welp reinstalling seemed to have broke more

[2024-05-09 15:39:18] Allnet | DEBUG | Allnet request: {'game_id': 'SDDT', 'ver': '1.40', 'serial': 'A69E01A8888', 'ip': '192.168.192.12', 'firm_ver': '50000', 'boot_ver': '0000', 'encode': 'UTF-8', 'hops': 1, 'format_ver': 3.0, 'token': '2697778582'}
[2024-05-09 15:39:18] Allnet | INFO | A69E01A8888 authenticated from 192.168.192.115: SDDT v1.40
[2024-05-09 15:39:18] Allnet | DEBUG | Allnet response: {'stat': 1, 'uri': 'http://artemis/SDDT/140/', 'host': 'artemis/', 'place_id': '0123', 'name': 'ARTEMiS', 'nickname': 'ARTEMiS', 'region0': '1', 'region_name0': 'W', 'region_name1': '', 'region_name2': '', 'region_name3': '', 'setting': '1', 'country': 'JPN', 'allnet_id': '123', 'client_timezone': '+0900', 'utc_time': '2024-05-09T15:39:18Z', 'res_ver': '3', 'token': '2697778582'}
[2024-05-09 15:39:18] Aimedb | ERROR | Error parsing ADB header: Status is incorrect! 49755 is not a valid ADBStatus
[2024-05-09 15:39:18] Aimedb | ERROR | Error parsing ADB header: Status is incorrect! 60488 is not a valid ADBStatus
[2024-05-09 15:39:18] Allnet | INFO | DownloadOrder from 192.168.192.115 -> SDDT v1.40 serial A69E01A8888
[2024-05-09 15:39:28] Billing | INFO | Billing checkin from 192.168.192.115: game SDDT ver 1.4 keychip A69E01A8888 playcount 0 billing_type A nearfull 512 playlimit 1024

welp reinstalling seemed to have broke more [2024-05-09 15:39:18] Allnet | DEBUG | Allnet request: {'game_id': 'SDDT', 'ver': '1.40', 'serial': 'A69E01A8888', 'ip': '192.168.192.12', 'firm_ver': '50000', 'boot_ver': '0000', 'encode': 'UTF-8', 'hops': 1, 'format_ver': 3.0, 'token': '2697778582'} [2024-05-09 15:39:18] Allnet | INFO | A69E01A8888 authenticated from 192.168.192.115: SDDT v1.40 [2024-05-09 15:39:18] Allnet | DEBUG | Allnet response: {'stat': 1, 'uri': 'http://artemis/SDDT/140/', 'host': 'artemis/', 'place_id': '0123', 'name': 'ARTEMiS', 'nickname': 'ARTEMiS', 'region0': '1', 'region_name0': 'W', 'region_name1': '', 'region_name2': '', 'region_name3': '', 'setting': '1', 'country': 'JPN', 'allnet_id': '123', 'client_timezone': '+0900', 'utc_time': '2024-05-09T15:39:18Z', 'res_ver': '3', 'token': '2697778582'} [2024-05-09 15:39:18] Aimedb | ERROR | Error parsing ADB header: Status is incorrect! 49755 is not a valid ADBStatus [2024-05-09 15:39:18] Aimedb | ERROR | Error parsing ADB header: Status is incorrect! 60488 is not a valid ADBStatus [2024-05-09 15:39:18] Allnet | INFO | DownloadOrder from 192.168.192.115 -> SDDT v1.40 serial A69E01A8888 [2024-05-09 15:39:28] Billing | INFO | Billing checkin from 192.168.192.115: game SDDT ver 1.4 keychip A69E01A8888 playcount 0 billing_type A nearfull 512 playlimit 1024
Collaborator

That aimedb error is most likely because you entered an invalid aimedb key in core.yaml

That aimedb error is most likely because you entered an invalid aimedb key in core.yaml
Author
Contributor

aimedb key is now 16 characters. That seems to not give the header error yeah thanks

aimedb key is now 16 characters. That seems to not give the header error yeah thanks
Author
Contributor

latest version everything fresh. It is now working

latest version everything fresh. It is now working
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Hay1tsme/artemis#137
No description provided.