[SalesForce] No log for Visualforce errors

I'm having a problem that I think has something to do with recent version because I don't remember having this problem before. Basically, when I have an error in a Visualforce page, I don't see the error in the Debug Log. I get an email with the error description, but it sometimes takes a long time to send it, so it's not very useful for debugging.

Any clues why an error in a Visualforce page is not showing in the debug log?

Error message example:

enter image description here

I added a System.debug('>>> fails here'); to understand the log better. This is the log from that point on:

13:50:49.723 (1723177000)|USER_DEBUG|[10]|DEBUG|>>> failing here
13:50:49.723 (1723184000)|SYSTEM_METHOD_EXIT|[10]|System.debug(ANY)
13:50:49.723 (1723261000)|SYSTEM_METHOD_ENTRY|[11]|MAP<String,Schema.DescribeSObjectResult>.put(Object, Object)
13:50:49.723 (1723288000)|SYSTEM_METHOD_EXIT|[11]|MAP<String,Schema.DescribeSObjectResult>.put(Object, Object)
13:50:49.723 (1723313000)|SYSTEM_METHOD_ENTRY|[12]|Schema.DescribeSObjectResult.getFields()
13:50:49.723 (1723354000)|SYSTEM_METHOD_EXIT|[12]|Schema.DescribeSObjectResult.getFields()
13:50:49.723 (1723376000)|SYSTEM_METHOD_ENTRY|[12]|Schema.SObjectTypeFields.getMap()
13:50:49.723 (1723581000)|SYSTEM_METHOD_EXIT|[12]|Schema.SObjectTypeFields.getMap()
13:50:49.723 (1723638000)|CONSTRUCTOR_EXIT|[106]|01pi00000059Qyc|<init>(LIST<String>)
13:50:49.723 (1723647000)|SYSTEM_MODE_EXIT|false
13:50:49.723 (1723847000)|CODE_UNIT_FINISHED|MeetingMaterialsController <init>
13:50:50.275 (1933543000)|CUMULATIVE_LIMIT_USAGE
13:50:50.275|LIMIT_USAGE_FOR_NS|(default)|

I can't understand why it doesn't show the null pointer exception or why the log is marked as "success". I used to get a stack at the point of the error inside the log.

Best Answer

There is an good trick to be able to see where the error null pointer occurs:

  • activate Development Mode in your profile

Without Development mode the system shows only the error message:

enter image description here

But if you activate the Development mode it shows the place in code where the error occurs:

enter image description here

Related Topic