When running an Angular app, I’m getting the following error in my browser console.
client.ts:80 Error parsing SSE: A2uiStateError: Surface weekend_planner_intro already exists.
at MessageProcessor.processCreateSurfaceMessage (message-processor.js:216:19)
at MessageProcessor.processMessage (message-processor.js:191:18)
at MessageProcessor.processMessages (message-processor.js:177:18)
at _A2uiRendererService.processMessages (a2ui-angular-v0_9.mjs:511:28)
at _Client.processParts (client.ts:102:21)
at _Client.handleStreamingResponse (client.ts:78:35)
at async _Client.makeRequest (client.ts:44:9)
at async _App.sendQuery (app.ts:19:5)You can reproduce this by simply running the restaurant_finder example. It still works, but I think this is an issue with how the streamed parts are being processed. My gut tells me that this has to do with the fact that each streamed chunk contains the entire response rather than a new part of the response, so it looks like the entire end response is being repeated several times from the client's perspective. That said, I can’t tell if this is an implementation issue or an SDK issue. If it’s an implementation issue, then I think all that’s needed would be to update the examples.
When running an Angular app, I’m getting the following error in my browser console.
client.ts:80 Error parsing SSE: A2uiStateError: Surface weekend_planner_intro already exists. at MessageProcessor.processCreateSurfaceMessage (message-processor.js:216:19) at MessageProcessor.processMessage (message-processor.js:191:18) at MessageProcessor.processMessages (message-processor.js:177:18) at _A2uiRendererService.processMessages (a2ui-angular-v0_9.mjs:511:28) at _Client.processParts (client.ts:102:21) at _Client.handleStreamingResponse (client.ts:78:35) at async _Client.makeRequest (client.ts:44:9) at async _App.sendQuery (app.ts:19:5)You can reproduce this by simply running the restaurant_finder example. It still works, but I think this is an issue with how the streamed parts are being processed. My gut tells me that this has to do with the fact that each streamed chunk contains the entire response rather than a new part of the response, so it looks like the entire end response is being repeated several times from the client's perspective. That said, I can’t tell if this is an implementation issue or an SDK issue. If it’s an implementation issue, then I think all that’s needed would be to update the examples.