-
Miguel Chinchilla - 4 years ago
-
Kirk Steffke - 4 years ago
@Miguel - when up against the issue and looking specifically for system.debugs, I find myself lowering the "Apex Code" Log Level down low enough that the ENTERING_MANAGED_PKGs no longer apply. I think "Warn" is the first level it stops including those. Then explicitly set my sys.debug levels to be "Warn" or lower.
IE: system.debug(LoggingLevel.ERROR, 'I want to see this');
Your mileage may vary as this is only helpful if the type of log information you are looking for isn't sitting at the same Levels as ENTERING_MANAGED_PAKAGE or you have a way to explicitly set their log level. For finding simple sys.debugs, this works for me. -
Miguel Chinchilla - 4 years ago
I have the same problem. Any Idea for remove this log "ENTERING_MANAGED_PKG".
Regards. -
Kirk Steffke - 5 years ago
I think it's important to note that there are actually two items to address in this idea:
a) The ability to filter out ENTERING_MANAGED_PKG messages - all orgs (dev or customer), regardless of the issue. In app-heavy orgs, you can quickly get to the log size limit.
b) Address the issue that causes the logging of ENTERING_MANAGED_PKG entries from within the org the package is being developed. It's entirely possible to see a debug log full of these entries, in the development org of a package, where no other Apps are installed. -
David Mosher - 5 years ago
This has been going on for years now. Clearly Salesforce doesn't care about how much time app developers are wasting trying to debug problems with the log files overflowing with this message even when you are in the source org with only 2 (TWO) methods. When you are in the source org this message clearly can be suppressed by the debug filter. This appears to happen when you define an object or structure in your package and then access (insert, update) outside of the package including in its own testmethod class that is in the package!!!!
When is Salesforce going to get serious about supporting its package developers???? -
Mike Katulka - 6 years ago
@mandar - That's unfortunate for you! I hope you can figure out a way to debug what you need. I've had to resort to a backup plan. Here are some ideas for you:
Overall, wrap more code in try/catch blocks so you can depend on the following options (don't forget to use database.rollback(savepoint) within the catch where necessary. Also track limits to leave room for the logging if you have issues with limits.- Use a custom object to store the logging that you are looking for.
- Use a public string variable in apex and send yourself an email at the end of execution.
- Create a VF page to fire off the code, and the string variable is shown on screen.
- For record level logging, create a debug field on the object that is being 'worked on' and debug into that field... might require that you DML update that object upon catching of an exception.
-
Mike Katulka - 6 years ago
This has been happening in a packaging org for me as well. There seems to be no way around it. Please vote up on this! -
Alex Sutherland - 6 years ago
Yeah, this is a really bad blocking issue for AppExchange developers. It SHOULD be a simple fix, hope it gets resolved soon! -
Keith Clarke - 6 years ago
I'm doing some debugging in Winter '15 with all categories set to "None" except Apex Code which is set to "Error" (to filter out as much as possible). Even after getting support to up the log size to the maximum of 10M bytes the information I need is off the end of the log because it is swamped by useless ENTERING_MANAGED_PKG entries. This is in the packaging org of one of our maaged packages.
So it looks to me like the problem still exists. -
Daniel Ballinger - 7 years ago
After further testing I've found that ENTERING_MANAGED_PKG appears only when the Apex Code Logging Level is Info or lower. For Warn or higher it doesn't appear.
How do you delete an idea?
Eric Kintzer - 4 years ago