Open JoseEstevesPt opened 6 months ago
manually editing catalog.xml and all plataform xml to use 50.2 instead of 51.0 fixed the error of invalid ane.
Connection to websocket works using this ANE, but my websocket server it's not receiving any data after i call _webSocket.sendMessage(WebSocket.fmtBINARY, sendBytes);
06-28 11:08:26.967 3013 4505 D AndroidSocketThread: Callback: onSendingHandshake
06-28 11:08:27.510 3013 4505 D AndroidSocketThread: Callback: onStateChanged
06-28 11:08:27.511 3013 4505 D AndroidSocketThread: Callback: onThreadCreated
06-28 11:08:27.512 3013 4505 D AndroidSocketThread: Callback: onThreadCreated
06-28 11:08:27.512 3013 4505 D AndroidSocketThread: Callback: onThreadStopping
06-28 11:08:27.513 3013 4523 D AndroidSocketThread: Callback: onThreadStarted
06-28 11:08:27.513 3013 4523 D AndroidSocketThread: Callback: onConnected
06-28 11:08:27.513 3013 4524 D AndroidSocketThread: Callback: onThreadStarted
06-28 11:08:27.522 3013 3013 D AndroidWebSocketSendMessage: Called sendMessage
06-28 11:08:27.522 3013 3013 D AndroidWebSocketSendMessage: Message is a byte array
06-28 11:08:27.522 3013 3013 E AndroidSocketThread: Eror sending bytes: null
manually editing catalog.xml and all plataform xml to use 50.2 instead of 51.0 fixed the error of invalid ane.
WebSocket
is a class introduced in AIR 51.0 so I'm a little surprised it works if you drop that down.
Although ... ah, I've just realised, we had a bug in how the platform descriptor files derived from earlier ones, which may have caused this. The fix is already in our internal builds, about to be released, so I wouldn't have seen that issue....
E AndroidSocketThread: Eror sending bytes: null
We'll have to check on this one.. are you able to confirm that you sent in a byte array (and presumably it wasn't null or empty)?
thanks
manually editing catalog.xml and all plataform xml to use 50.2 instead of 51.0 fixed the error of invalid ane.
WebSocket
is a class introduced in AIR 51.0 so I'm a little surprised it works if you drop that down.Although ... ah, I've just realised, we had a bug in how the platform descriptor files derived from earlier ones, which may have caused this. The fix is already in our internal builds, about to be released, so I wouldn't have seen that issue....
E AndroidSocketThread: Eror sending bytes: null
We'll have to check on this one.. are you able to confirm that you sent in a byte array (and presumably it wasn't null or empty)?
thanks
Yeah.. sending byteArray.
private function sendConfirmConnection():void
{
var sendBytes:ByteArray =new ByteArray();
sendBytes.writeUTF(RandomUtils.UIDv4());
sendBytes.writeUTF("confirm-connection");
sendBytes.writeInt(_areaId);
sendBytes.writeUTF("token");
sendBytes.writeBoolean(_wsConnectionId != null);
if (_wsConnectionId != null)
{
sendBytes.writeUTF(_wsConnectionId);
}
_webSocket.sendMessage(WebSocket.fmtBINARY, sendBytes);
}
My implementation it's working normally for windows, i just made a change to use AndroidWebSocket instead of WebSocket..
Hi
You can try this one, it fixes an issue with sending and receieving ByteArray data..
thanks
I'm using Adobe Animate 24.0.3 and Air SDK 50.2.4.4, creating a desktop app that connects do websockets (websockt or websocket IO) server, I've tried all the old libraries, help of chat GPT, help of Copilot, nothing works. Then I saw this post...How can I get AIR SDK 51? will I be able to solve my problem. Please help!
Discussed in https://github.com/airsdk/Adobe-Runtime-Support/discussions/3081