You need to sign in to do that
Don't have an account?
Mae Legaspi
Lightning Component Assertion Failed!: Provider type not supported : false
We have a VF page that basically just embeds a lightning component. We've been using this page for some time now, but then it just suddenly stopped working and showed the error:
Then when I tried to create a Lightning App Page via the Lightning App Builder and incorporate the same lightning component we used on the VF page, I got the following error:
Is there an Aura update on Salesforce that could have possibly caused this?
We didn't modify anything on our code base, and the error also suddenly appeared on our sandbox, which was created days before this happened. This is why we're thinking there must be some changes on Salesforce's side we're not aware of.
This page has an error. You might just need to refresh it. Assertion Failed!: Provider type not supported : false Failing descriptor: {c:LeadSearchBar}Refreshing the page didn't help. Not sure if it's related, but I saw this on the console logs:
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://ourcompany.lightning.force.com') does not match the recipient window's origin ('https://ourcompany.cs94.my.salesforce.com').No error on the actual debug logs.
Then when I tried to create a Lightning App Page via the Lightning App Builder and incorporate the same lightning component we used on the VF page, I got the following error:
A Component Error has occurred! Message: Assertion Failed!: Provider type not supported : false Component Descriptor: markup://c:LeadSearchBar Filename: https://ourcompany.lightning.force.com/auraFW/javascript/m1kqsGvUD3kBv3RmG5pSKA/aura_prod.js Function: QA.log Line: 237 Column: 157 Stack Trace: QA.log()@https://ourcompany.lightning.force.com/auraFW/javascript/m1kqsGvUD3kBv3RmG5pSKA/aura_prod.js:237:157 $.z.assert()@https://ourcompany.lightning.force.com/auraFW/javascript/m1kqsGvUD3kBv3RmG5pSKA/aura_prod.js:784:397 a.P.Pd()@https://ourcompany.lightning.force.com/auraFW/javascript/m1kqsGvUD3kBv3RmG5pSKA/aura_prod.js:390:477 a.P [as constructor]()@https://ourcompany.lightning.force.com/auraFW/javascript/m1kqsGvUD3kBv3RmG5pSKA/aura_prod.js:388:428 new a()@https://ourcompany.lightning.force.com/auraFW/javascript/m1kqsGvUD3kBv3RmG5pSKA/aura_prod.js:275:254 V.Db()@https://ourcompany.lightning.force.com/auraFW/javascript/m1kqsGvUD3kBv3RmG5pSKA/aura_prod.js:639:465 a.z.Pd()@https://ourcompany.lightning.force.com/auraFW/javascript/m1kqsGvUD3kBv3RmG5pSKA/aura_prod.js:333:140
Is there an Aura update on Salesforce that could have possibly caused this?
We didn't modify anything on our code base, and the error also suddenly appeared on our sandbox, which was created days before this happened. This is why we're thinking there must be some changes on Salesforce's side we're not aware of.
Looks like Salesforce enhanced their javascript QA tool that's why the error has been caught this time (tho it still kinda sucks that the error message and stack trace didn't really help). I guess our lightning component never really fully worked as expected before.
Thanks to everyone who took the time to read my post!
All Answers
I believe this is happening because the of the changes made to URL structure in the summer'1 release.
I might be able to help you if you could just share your code.
Looks like Salesforce enhanced their javascript QA tool that's why the error has been caught this time (tho it still kinda sucks that the error message and stack trace didn't really help). I guess our lightning component never really fully worked as expected before.
Thanks to everyone who took the time to read my post!