Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

creation d'un User avec le SDK return un Object avec le champs ID absent #412

Open
gaschard opened this issue Jun 17, 2024 · 6 comments
Open

Comments

@gaschard
Copy link

Bonjour la team Mangopay

nous utilisons votre SDK : https://www.npmjs.com/package/mangopay2-nodejs-sdk

Nous avons remarqué depuis 1 semaine que la fonction de création d'un nouveau User via l'API mangopay sur le sandbox (TOUT MARCHE nickel EN PROD) retourne :

  • un Object qui ressemble à un buffer
  • avec le champ ID absent.

Voici un dump de la réponse que nous obtenons ...

child {
'0': 123,
'1': 34,
'2': 65,
'3': 100,
'4': 100,
......
'667': 34,
'668': 125,
readBigUInt64LE: [Function: readBigUInt64LE],
readBigUInt64BE: [Function: readBigUInt64BE],
readBigUint64LE: [Function: readBigUInt64LE],
readBigUint64BE: [Function: readBigUInt64BE],
readBigInt64LE: [Function: readBigInt64LE],
readBigInt64BE: [Function: readBigInt64BE],
writeBigUInt64LE: [Function: writeBigUInt64LE],
writeBigUInt64BE: [Function: writeBigUInt64BE],
writeBigUint64LE: [Function: writeBigUInt64LE],
writeBigUint64BE: [Function: writeBigUInt64BE],
writeBigInt64LE: [Function: writeBigInt64LE],
writeBigInt64BE: [Function: writeBigInt64BE],
readUIntLE: [Function: readUIntLE],
readUInt32LE: [Function: readUInt32LE],
readUInt16LE: [Function: readUInt16LE],
readUInt8: [Function: readUInt8],
readUIntBE: [Function: readUIntBE],
readUInt32BE: [Function: readUInt32BE],
readUInt16BE: [Function: readUInt16BE],
readUintLE: [Function: readUIntLE],
readUint32LE: [Function: readUInt32LE],
readUint16LE: [Function: readUInt16LE],
readUint8: [Function: readUInt8],
readUintBE: [Function: readUIntBE],
readUint32BE: [Function: readUInt32BE],
readUint16BE: [Function: readUInt16BE],
readIntLE: [Function: readIntLE],
readInt32LE: [Function: readInt32LE],
readInt16LE: [Function: readInt16LE],
readInt8: [Function: readInt8],
readIntBE: [Function: readIntBE],
readInt32BE: [Function: readInt32BE],
readInt16BE: [Function: readInt16BE],
writeUIntLE: [Function: writeUIntLE],
writeUInt32LE: [Function: writeUInt32LE],
writeUInt16LE: [Function: writeUInt16LE],
writeUInt8: [Function: writeUInt8],
writeUIntBE: [Function: writeUIntBE],
writeUInt32BE: [Function: writeUInt32BE],
writeUInt16BE: [Function: writeUInt16BE],
writeUintLE: [Function: writeUIntLE],
writeUint32LE: [Function: writeUInt32LE],
writeUint16LE: [Function: writeUInt16LE],
writeUint8: [Function: writeUInt8],
writeUintBE: [Function: writeUIntBE],
writeUint32BE: [Function: writeUInt32BE],
writeUint16BE: [Function: writeUInt16BE],
writeIntLE: [Function: writeIntLE],
writeInt32LE: [Function: writeInt32LE],
writeInt16LE: [Function: writeInt16LE],
writeInt8: [Function: writeInt8],
writeIntBE: [Function: writeIntBE],
writeInt32BE: [Function: writeInt32BE],
writeInt16BE: [Function: writeInt16BE],
readFloatLE: [Function: readFloatForwards],
readFloatBE: [Function: readFloatBackwards],
readDoubleLE: [Function: readDoubleForwards],
readDoubleBE: [Function: readDoubleBackwards],
writeFloatLE: [Function: writeFloatForwards],
writeFloatBE: [Function: writeFloatBackwards],
writeDoubleLE: [Function: writeDoubleForwards],
writeDoubleBE: [Function: writeDoubleBackwards],
asciiSlice: [Function: asciiSlice],
base64Slice: [Function: base64Slice],
base64urlSlice: [Function: base64urlSlice],
latin1Slice: [Function: latin1Slice],
hexSlice: [Function: hexSlice],
ucs2Slice: [Function: ucs2Slice],
utf8Slice: [Function: utf8Slice],
asciiWrite: [Function: asciiWrite],
base64Write: [Function: base64Write],
base64urlWrite: [Function: base64urlWrite],
latin1Write: [Function: latin1Write],
hexWrite: [Function: hexWrite],
ucs2Write: [Function: ucs2Write],
utf8Write: [Function: utf8Write],
parent: ArrayBuffer {
[Uint8Contents]: <7b 22 41 64 64 72 65 73 73 22 3a 7b 22 41 64 64 72 65 73 73 4c 69 6e 65 31 22 3a 6e 75 6c 6c 2c 22 41 64 64 72 65 73 73 4c 69 6e 65 32 22 3a 6e 75 6c 6c 2c 22 43 69 74 79 22 3a 6e 75 6c 6c 2c 22 52 65 67 69 6f 6e 22 3a 6e 75 6c 6c 2c 22 50 6f 73 74 61 6c 43 6f 64 65 22 3a 6e 75 6c 6c 2c 22 43 6f 75 ... 8092 more bytes>,
byteLength: 8192
},
offset: 0,
copy: [Function: copy],
toString: [Function: toString],
equals: [Function: equals],
inspect: [Function: inspect],
compare: [Function: compare],
indexOf: [Function: indexOf],
lastIndexOf: [Function: lastIndexOf],
includes: [Function: includes],
fill: [Function: fill],
write: [Function: write],
toJSON: [Function: toJSON],
slice: [Function: slice],
swap16: [Function: swap16],
swap32: [Function: swap32],
swap64: [Function: swap64],
toLocaleString: [Function: toString],
PersonType: 'NATURAL'
}

@stephen-shopopop
Copy link

L’origine de l’erreur provient du header "content-type" de la reponse:

Content-Type: application/json; charset=utf-8; x-api-version=2.1

Ticket ouvert sur derniere version du sdk: #413

@gaschard
Copy link
Author

gaschard commented Jun 19, 2024 via email

@stephen-shopopop
Copy link

Il faut se rapprocher de mangopay a cet effet. Nous avons juste fait le meme constat et trouvé l'origine.

@gaschard
Copy link
Author

gaschard commented Jun 19, 2024 via email

@stephen-shopopop
Copy link

stephen-shopopop commented Jul 13, 2024

Cela semble être résolu. Le header correspondant à été fix sur sandbox.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants