- Newest
- Most votes
- Most comments
Hi there,
Thank you for posting the question. In order to troubleshoot this issue further, please provide the following details :
-
Are you calling embeddedQBarExperience.close()? Based on the error provided, it looks like the close function times out in communicating with the embedded content, which may indicate the embedded content is not (yet) loaded.
-
Can you please confirm error is showing onscreen, not just in the console. Also can you share the complete error message.
If you are still facing the issue, can you please open a support case with AWS using the following link and we will be happy to help you.
Thank you!
- No, not calling close function on embeddedQBarExperience. Listening to events of Q_SEARCH_CLOSE, which only has a console log.
- Yes, the error is coming on screen too as it's unhandled run time error. Screen Error:
Uncaught runtime errors: × ERROR CLOSE_Q_SEARCH timed out at handleError (https://<host>:<port>/static/js/bundle.js:532096:58) at https://<host>:<port>/static/js/bundle.js:532119:7
Console error: Uncaught (in promise) CLOSE_Q_SEARCH timed out setTimeout (async) (anonymous) @ experience-frame.ts:125 (anonymous) @ experience-frame.ts:96 ............. ............. (anonymous) @ experience-frame.ts:131 (anonymous) @ base-experience.ts:89 ............. ............. (anonymous) @ base-experience.ts:92 (anonymous) @ q-search-experience.ts:63
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Some additional error logs: Uncaught (in promise) CLOSE_Q_SEARCH timed out setTimeout (async) (anonymous) @ experience-frame.ts:125 (anonymous) @ experience-frame.ts:96