cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
556
Views
0
Helpful
1
Replies

Embedded meeting - getUser Error: NOT_SUPPORTED

lbslbm0iz2
Level 1
Level 1

Hello.

I've put together an embedded app and am trying to access the user id. When I attempt getUser I receive an error 6 - NOT_SUPPORTED. From the documentation, I can't see why that might be. I'm running this in the development console belonging to the app session in a Meeting as follows:

 

window.webexInstance.context.getUser().then((user) => {
    console.log("user", user)
}).catch((errorcode) => {
    console.log("Error", errorcode)
});

 

And that produces the following output

 

[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:56:19.143Z" RequestManager: set: requestId=wzptvfi6o7tcz5b25bwt request=application.context.getUser
< Promise {status: "pending"}
[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:56:19.151Z" ApplicationApi: SDK received requestId wzptvfi6o7tcz5b25bwt
[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:56:19.151Z" ApplicationApi: handleNativeResponse: response: request=application.context.getUser requestId=wzptvfi6o7tcz5b25bwt
[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:56:19.151Z" RequestManager: setLastError: request=application.context.getUser code=6
[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:56:19.151Z" RequestManager: delete: requestId=wzptvfi6o7tcz5b25bwt request=application.context.getUser
[Log] Error – 6

 

I've looked up Error Code 6, and it corresponds with NOT_SUPPORTED - "Call failed because the feature is not supported."

Curiously running getMeeting in the same context works fine

 

window.webexInstance.context.getMeeting().then((meeting) => {
    console.log("meeting: ", meeting)
}).catch((errorcode) => {
    console.log("Error", errorcode)
});

 

Producing the following output

 

[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:53:01.683Z" RequestManager: set: requestId=s2ot96dcvpbr1c8m9cixd request=application.context.getMeeting
< Promise {status: "pending"}
[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:53:01.693Z" ApplicationApi: SDK received requestId s2ot96dcvpbr1c8m9cixd
[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:53:01.693Z" ApplicationApi: handleNativeResponse: response: request=application.context.getMeeting requestId=s2ot96dcvpbr1c8m9cixd
[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:53:01.693Z" ApplicationApi: update: application.context.getMeeting
[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:53:01.694Z" RequestManager: setLastError: request=application.context.getMeeting code=0
[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:53:01.694Z" RequestManager: delete: requestId=s2ot96dcvpbr1c8m9cixd request=application.context.getMeeting
[Log] [INFO - (sdk)] timestamp: "2023-09-29T05:53:01.694Z" ApplicationApi: resolve msg: request=application.context.getMeeting
[Log] meeting:  – {conferenceId: "272897613835060617", displayName: "", endTime: "2023-09-29T06:10:00.000Z", …}
{conferenceId: "272897613835060617", displayName: "", endTime: "2023-09-29T06:10:00.000Z", id: "e5864c63a49243e0ba545e06e0dd3129", instanceId: "9537a63d-14f0-5578-93f4-26629537e486", …}Object

 

 I do have PII enabled - though I wouldn't have thought it was necessary as I'm not attempting to access emails, etc.

Is there something I'm missing?

1 Accepted Solution

lbslbm0iz2
Level 1
Level 1

Turns out I was using the v1 api docs, not v2.

Screenshot 2023-09-29 at 21.08.22.png

View solution in original post

1 Reply 1

lbslbm0iz2
Level 1
Level 1

Turns out I was using the v1 api docs, not v2.

Screenshot 2023-09-29 at 21.08.22.png