While attempting to use our currently existing visualforce pages in Salesforce 1, we're greeted with an error message that says: "Javascript proxies were not generated for controller : may not use public remoted methods inside an iframe."

I have found one solution that says to make all of our remote actions global but since we are working with a managed package that would also mean making changes to those remote actions down the line could really be an issue, and it would allow access to functionality that I would rather not expose. Is there something along the way that we may have missed, or is this truly the only way? At the moment I am considering writing an API of sorts to add a layer between our proprietary functionality.. but that also seems messy.


  • 1
    This would be a regression in functionality and not intended. If you file a bug it would get fixed.
    – Kris Gray
    Commented Jun 23, 2014 at 19:20
  • 1
    Is this still happening?
    – Kris Gray
    Commented Jul 16, 2014 at 23:15
  • yeah we've currently escalated the issue with our AE but no concrete response yet. I will update the question if/when we get one.. Commented Jul 17, 2014 at 23:22
  • answered my own quesiton - had to do with window.location.. see salesforce.com/us/developer/docs/salesforce1/Content/… for more! Commented Jul 24, 2014 at 21:44

1 Answer 1


Turns out the issue was with how we were doing redirection on our landing page. We were using window.location to handle a custom redirect (dynamic page names), and this was causing salesforce1 to behave oddly. Since the rest of our application used Page refs to handle redirection there were no issues but once the app was iframed it was left in that state. Funny enough this is in the salesforce 1 documentation..


But it was not something we had considered up until this point.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .