Switching from Lightning to Classic View fails with Gack
Last updated 2022-02-10 ·Reference W-3194761 ·Reported By 9 users
Summary
Switching from Lightning to Classic View fails with Gack instead of a valid error. When a user switch between Lightning to Classic View, all validation rules are run on user object and if any of the Validation rule fails instead of throwing the validation rule error messages a Gack is thrown.
Expected Result- Correct validation rule error message should be displayed to user
Actual results- A gack is thrown "Sorry to Interrupt-
This page has an error. You might just need to refresh it. First, would you give us some details? (We're reporting this as error ID: d76cf9e7-4a19-4036-9c9a-3c7a07456ac2)
Uncaught Error in $A.getCallback() [[object Object]]
throws at https://na28.lightning.force.com/auraFW/javascript/HARM87fxppWmsEY_Ve9awQ/aura_prod.js:1:27
[anonymous]
at Ry
at [anonymous]
at [anonymous]
at [anonymous]
at [anonymous]
at [anonymous]
at EA
at [anonymous]
at [anonymous]
at [anonymous] (Recursion Entry Point)
Repro
The issue can be replicated in any Summer 16 org by creating a simple validation rule on user object and switching to classic view from Lightning for a user for which Validation rule will fail.
Workaround
Fix the user record not to throw the Validation error
Eg- Check if you have recently made any change in Validation Rules or user record which would make any validation rule fail for the user record.
Please Note- Once the bug us fixed the validation error message will be thrown instead of a gack
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.
