Post date: Feb 04, 2021 3:57:59 PM
2.1.5.8
Issue 1801 (redux) - Improved end user feedback when the workaround for the INVALID_CROSS_REFERENCE_KEY Tooling API deployment error is applied:
If the error was encountered but the Tooling API deployer is able to complete the request, the status is changed to warning (if not already warning or error) and a message is added to the deployment details in the Messages tool window that the API error was encountered and may have lengthened the deployment time. The user is advised that Tooling API-based deployment of Apex and Visualforce should perhaps be disabled until Salesforce issues a fix.
If the error was encountered and the allowed retry count (10) was exceeded, the user is notified about the nature of the deployment failure and is prompted to disable Tooling API-based deployment of Apex and Visualforce until Salesforce issues a fix.
Issue 1583 - Fixed an issue with the log-based debugger that prevented it from stepping into mock callouts and Web services properly. Note that this requires the Callout log level to be raised to a minimum of INFO. All affected log level presets have been adjusted accordingly.
Improved the display and behavior of Apex test stubs/mocks in the log-based debugger.
Adjusted the way that stack frames for system types are displayed in the log-based debugger. They are now grayed to provide a visual distinction between stack frames in system types and those in custom types.
Fixed an issue that could occur when trying to execute a unit test run configuration for profiling where the Log Analyzer profiling view wouldn't be automatically displayed upon test completion.
Other related fixes and improvements.