[desktop-viewer] stuck loading while fetching imodels

[edemiaochu]

in desktop-viewer-react project, when i use npm start, the imodels page keeps loading. when i use serve -s ./build ,the imodels page can load normally. why?

[edemiaochu]

sorry ,in desktop-viewer-test project.

[aruniverse]

Hi! Have you inspected the network tab? Are the requests to api.bentley.com/imodels resolving?

[edemiaochu]

Hi，And, when i run npm start to start, the file opened is snapshotconnection,can't edit,but,when i use serve -s ./build and npm run electron:debug to start, the opened file is briefcaseconnection, do you konw why?

[edemiaochu]

Hi! Have you inspected the network tab? Are the requests to api.bentley.com/imodels resolving?

H i，yes ，the status is 200

[MichaelSwigerAtBentley]

Hi, to clarify, does the iModels page keep loading when attempting to access a specific iTwin's iModels via the 'downloads' option?

[edemiaochu]

Hi, to clarify, does the iModels page keep loading when attempting to access a specific iTwin's iModels via the 'downloads' option?

Hi , no, imodels keep loading. I can't see download option.[when i run 'npm start']

[MichaelSwigerAtBentley]

Hi, I'm having trouble recreating this.

When running npm start from the viewer\packages\apps\desktop-viewer-test App.tsx is called, which should load the Home.tsx file.

Could you post your console out? Its possible something is occurring during App.tsx initialization

[edemiaochu]

Hi, Do you mean these ? One is backend console out ,the other is frontend console out

[edemiaochu]

Hi, Do you mean these ? One is backend console out ,the other is frontend console out

[MichaelSwigerAtBentley]

Yes, those were the consoles I was referring to, thanks

[MichaelSwigerAtBentley]

I believe I have recreated the issue.

A function seems to be aborting the imodels api calls before they can fully resolve.

It seems possible that when you use npm start to start, the app is making a request for an iTwin via an api call and that request is timing out. The preflight handshake might be returning 200, which is what you are seeing, but the actual response never arrives. When you use serve you are loading a local .bim file, which is working as normal, thus the discrepancy.

Could you take a screenshot of your network tab while searching for api.bentley.com/imodels requests?

[MichaelSwigerAtBentley]

A potential solution:

At lines 31 and 33 in \viewer\packages\apps\desktop-viewer-test\src\frontend\index.tsx, there is a React.StrictMode wrapper.

Try removing that wrapper, then rebuild and attempt the api call again.

[edemiaochu]

Hi，it worked. Thank you very much. By the way , Would it fix in Viewer's next  version ?

[MichaelSwigerAtBentley]

Yes, this will be resolved in the next version. Thanks for reporting the issue!