You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received type number (
#371
"TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received type number ({machine ID goes here})" Shows up after a successful log on.
This is coming from ...\steam-user\components\logon.js:294:18
when it attempts to save the machine id: this.storage.saveFile('cellid-' + Helpers.getInternalMachineID() + '.txt', body.cell_id);
I believe node stopped automatically fixing types in a newer update, a simple fix to this would be to convert body.cell_id to a string. I used toString(body.cell_id) as a duct tape fix, but there may be better or more secure ways to do it. I can submit a pull request if you think this is a valid solution 😄
Versions
Node v16.3.0 and Steam-user 4.19.12
Screenshots and Error Logs
The text was updated successfully, but these errors were encountered:
Describe the bug
"TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received type number ({machine ID goes here})" Shows up after a successful log on.
This is coming from ...\steam-user\components\logon.js:294:18
when it attempts to save the machine id:
this.storage.saveFile('cellid-' + Helpers.getInternalMachineID() + '.txt', body.cell_id);
I believe node stopped automatically fixing types in a newer update, a simple fix to this would be to convert body.cell_id to a string. I used
toString(body.cell_id)
as a duct tape fix, but there may be better or more secure ways to do it. I can submit a pull request if you think this is a valid solution 😄Versions
Node v16.3.0 and Steam-user 4.19.12
Screenshots and Error Logs
The text was updated successfully, but these errors were encountered: