Timeline for Managed package gives lightning out syntax error after adding the handling of an application event
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 2, 2016 at 12:22 | comment | added | Surya Chandra Rao Gandreddi | Any solutions?? | |
| Oct 19, 2016 at 10:16 | comment | added | Stephen Roden | @DougChasman, you haven't mentioned what the approved pattern is for trapping lighting events in Visualforce pages. Can you point us at the documentation? | |
| Sep 20, 2016 at 13:55 | comment | added | Jovabe | The error remains if I comment out that line and repackage. I'll try to backtrack my changes some more until I get it working again. Could you tell me what pattern is supported? | |
| Sep 20, 2016 at 13:21 | comment | added | Doug Chasman | I just noticed that you are using an undocumented ($A.eventService.addHandler) and unsupported API to wire up handleNavToURL(). We're going to need to change that (there is a pattern that is supported) but I am not convinced that would fix this access check related issue (can't tell what component, event, attribute, etc is triggering this server side exception since its not part of the aura:noAccess event's attributes. Does the problem persist if you temporarily comment out the call to $A.eventService.addHandler()? | |
| Sep 20, 2016 at 13:00 | comment | added | Jovabe | OK. If it helps I shared my github repository of the managed package code in the support case with Sandeep. Although it's a public repository, I'd prefer not to share it on a public site. | |
| Sep 20, 2016 at 12:58 | comment | added | Doug Chasman | We are investigating - I do not believe there is anything in your code that is causing this and it looks like a system level issue. | |
| Sep 19, 2016 at 12:37 | comment | added | Jovabe | Thank you for responding. I already have access="GLOBAL" inside the component though. | |
| Sep 16, 2016 at 19:59 | history | answered | Doug Chasman | CC BY-SA 3.0 |