function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Vinicius ZVinicius Z 

VisualForce page not resuming properly on Salesforce1

Hi all,

I have an error that is thrown whenever I have a Visualforce page open on Salesforce1 and tab to another application on my phone.
Upon resuming the Salesforce1 app, it presents an error message that goes:
Access Check Failed! 
EventService.getEventDef():'markup://native:appresumed' is not visible to 'undefined'.

That happens even when resuming a blank VisualForce page with no controller. Could it be any settings on the Saleforce1 app that we are missing? Any help or related experiences will be thoroughly appreciated.

NagendraNagendra (Salesforce Developers) 
Hi Diogo,

You can fix access check errors using one or more of these techniques.
  1. Add appropriate access system attributes to the resources that you own.
  2. Remove references in your code to resources that aren’t available. In the earlier example, markup://c:targetComponent doesn’t have an access value allowing markup://c:sourceComponent to access it.
  3. Ensure that an attribute that you’re accessing exists by looking at its <aura:attribute> definition. Confirm that you’re using the correct case-sensitive spelling for the name.
  4. Accessing an undefined attribute or an attribute that is out of scope, for example, a private attribute triggers the same access violation message. The access context doesn’t know whether the attribute is undefined or inaccessible.
Note: If your code isn’t working as you expect, enable debug mode to get better error reporting.

Example: is not visible to 'undefined'
ComponentService.getDef():'markup://c:targetComponent' is not visible to 'undefined'
The key word in this error message is undefined, which indicates that the framework has lost context. This happens when your code accesses a component outside the normal framework lifecycle, such as in a setTimeout() or setInterval()call or in an ES6 Promise.

Fix this error by wrapping the code in a $A.getCallback() call.For more information, see Modifying Components Outside the Framework Lifecycle(

Please mark this as solved if it's resolved.