Return to Question

"Visualforce Remoting: Javascript proxies were not generated for controller xyz: may not use public remoted methods inside an iframe." Getting this error when I am using my pages in lightening. I am getting this wherever I have used remote actions. If I make remote actions global this error is gone. But I don't want this as solution because, to make all remote actions global I need to make classes as global also. Works fine in Salesforce Classic

"Visualforce Remoting: Javascript proxies were not generated for controller xyz: may not use public remoted methods inside an iframe." Getting this error when I am using my pages in Lightning. I am getting this wherever I have used remote actions. If I make remote actions global this error is gone. But I don't want this as solution because, to make all remote actions global I need to make classes as global also. Works fine in Salesforce Classic

"Visualforce Remoting: Javascript proxies were not generated for controller TemplateManagerController: may not use public remoted methods inside an iframe." Getting this error when I am using my pages in lightening. I am getting this wherever I have used remote actions. If I make remote actions global this error is gone. But I don't want this as solution because, to make all remote actions global I need to make classes as global also. Works fine in Salesforce Classic

"Visualforce Remoting: Javascript proxies were not generated for controller xyz: may not use public remoted methods inside an iframe." Getting this error when I am using my pages in lightening. I am getting this wherever I have used remote actions. If I make remote actions global this error is gone. But I don't want this as solution because, to make all remote actions global I need to make classes as global also. Works fine in Salesforce Classic