UCWA消息处理异常：获取Incoming消息href时出现undefined错误

Let's break down the issue you're facing and fix the code step by step. The core problem here is a combination of unlinked variables and missing safety checks for nested data structures in the UCWA Event API response.

What's Going Wrong #

Your console.log(messageIn) shows the expected resources, but the subsequent code tries to use link and embed variables that aren't connected to the messageIn array you built. Additionally, you're accessing nested properties without verifying they exist first—this is why you're hitting the undefined error when checking embed.message.direction.

Fixed Code Example #

Here's the adjusted code with key fixes and safety checks:

SkypeService.getEvent(msg).then(function (result) { 
    msg.eventsNext = result._links.next.href; 
    if (result && result.sender && result.sender.length > 0) { 
        for (var item in result.sender) { 
            var ref = result.sender[item].events; 
            for (var key in ref) { 
                // Push the full event object (not just _embedded) to keep _links context
                messageIn.push(ref[key]); 
            } 
        } 
    } 
    console.log(messageIn);

    // Iterate through collected events to find incoming messages
    messageIn.forEach(function(event) {
        // First confirm the event is a message type
        if (event._links && event._links.rel === 'message') { 
            console.log("message is there");
            // Check if the embedded message exists before accessing it
            if (event._embedded && event._embedded.message) { 
                console.log("links exist");
                var incomingMessage = event._embedded.message;
                // Verify direction exists before checking its value
                if (incomingMessage.direction && incomingMessage.direction === "Incoming") { 
                    console.log("direction is there");
                    // Use optional chaining to safely access nested hrefs
                    msg.participant = incomingMessage._links.participant?.href;
                    msg.contMsg = incomingMessage._links.messaging?.href;
                    msg.msgIn = incomingMessage._links.plainMessage?.href;
                }
            }
        }
    });
});

Key Fixes Explained #

1. Link Variables to Collected Events
   The original code pushed only _embedded data to messageIn and then referenced undefined link/embed variables. We now push the full event object and iterate through messageIn to access each event's _links and _embedded properties directly.

2. Add Safety Checks for Nested Properties
   UCWA responses may have missing nested fields depending on the event type. We added checks for event._links, event._embedded.message, and incomingMessage.direction to prevent undefined errors when accessing these properties.

3. Use Optional Chaining for Robustness
   The ?. operator safely accesses nested hrefs—if a parent property like _links.participant doesn't exist, it returns undefined instead of throwing an error.

4. Preserve Full Event Context
   By pushing the complete event object to messageIn, we retain the _links data needed to identify message-type events.

Since your conversation is already active (no accept href needed), this code will correctly capture the messaging and plainMessage hrefs you need to send a reply back to the Bot.

内容的提问来源于stack exchange，提问作者Heather