Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

react-accordion throwing exceptions #1270

Closed
shahzeb85 opened this issue May 1, 2020 · 12 comments
Closed

react-accordion throwing exceptions #1270

shahzeb85 opened this issue May 1, 2020 · 12 comments
Labels
status:incomplete-submission Submitter didn't fill the issue template. Issue automatically closed.

Comments

@shahzeb85
Copy link

Unhandled promise rejection [SPLoaderError.urlStatusHttpsNetworkErrorError]:

***Failed to load URL 'https://something-portal1.sharepoint.com/sites/apps/ClientSideAssets/6d6cf05b-cfe5-4d12-af19-19ec3aedcaf9/react-accordion-reactaccordionwebpartstrings_en-us_9fcb7072aaced7a537ba942e689d468d.js' for resource 'ReactAccordionWebPartStrings' in component '97a28c00-64ee-4ec7-b373-723e39069a96' (ReactAccordionWebPart). There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.

SEC7120: [CORS] The origin 'https://something.sharepoint.com' did not find 'https://something.sharepoint.com' in the Access-Control-Allow-Origin response header for cross-origin script resource at 'https://something-portal1.sharepoint.com/sites/apps/ClientSideAssets/6d6cf05b-cfe5-4d12-af19-19ec3aedcaf9/react-accordion-controlstrings_en-us_9d5c960645bbbbf6af0dced2dc36c079.js'.

Just added the webpart and created the back-end list. Any help would be appreciated

@ghost
Copy link

ghost commented May 1, 2020

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@ghost ghost added the Needs: Triage 🔍 label May 1, 2020
@larraiz
Copy link

larraiz commented May 1, 2020

are you are running the webpart on workbench page?

@larraiz
Copy link

larraiz commented May 1, 2020

Also you need to run this command gulp trust-dev-cert. in order to allow runnig https page on localhost environment.

@shahzeb85
Copy link
Author

No. on actual spo site

@larraiz
Copy link

larraiz commented May 1, 2020

I just added it to my development tenant and it's working well, have you tried with another web part?

@shahzeb85
Copy link
Author

shahzeb85 commented May 1, 2020

no just this webpart. I will try on different site.

@shahzeb85
Copy link
Author

shahzeb85 commented May 1, 2020

It works but I still see exceptions in browser console. Do you?

@larraiz
Copy link

larraiz commented May 2, 2020

Those exceptions are related to the webpart?. because SPO sometimes shows exception on console related to something else.

@shahzeb85
Copy link
Author

So shall I ignore this:
SEC7120: [CORS] The origin 'https://something.sharepoint.com' did not find 'https://something.sharepoint.com' in the Access-Control-Allow-Origin response header for cross-origin script resource at 'https://something-portal1.sharepoint.com/sites/apps/ClientSideAssets/6d6cf05b-cfe5-4d12-af19-19ec3aedcaf9/react-accordion-controlstrings_en-us_9d5c960645bbbbf6af0dced2dc36c079.js'.

@larraiz
Copy link

larraiz commented May 2, 2020

@shahzeb85 you can look at this post, SharePoint/sp-dev-gdpr-activity-hub#51
it's could be something related to the loc-string file or like I said at begining, you have to install the gulp dev certificate and bundle the webpart again.

@shahzeb85
Copy link
Author

Again getting this exception today on my page. I tried gulp trust-dev-cert but no difference.
***Failed to load URL 'https://something-portal1.sharepoint.com/sites/apps/ClientSideAssets/6d6cf05b-cfe5-4d12-af19-19ec3aedcaf9/react-accordion-reactaccordionwebpartstrings_en-us_9fcb7072aaced7a537ba942e689d468d.js' for resource 'ReactAccordionWebPartStrings' in component '97a28c00-64ee-4ec7-b373-723e39069a96' (ReactAccordionWebPart). There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.

@hugoabernier hugoabernier added the status:incomplete-submission Submitter didn't fill the issue template. Issue automatically closed. label May 6, 2020
@hugoabernier
Copy link
Collaborator

Closing this issue as invalid.

If you're still running into this issue, feel free to open a new one. If you do, please take the time to fill the issue template provided so that we can help you better. Incomplete issues are automatically closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:incomplete-submission Submitter didn't fill the issue template. Issue automatically closed.
Projects
None yet
Development

No branches or pull requests

3 participants