We've been experiencing an issue just after Winter '21 that on objects that have been overridden by a Visualforce Page for New button, the New action only works first time, if users instead of clicking Save, clicks Cancel button then user has to logout and log back in to use the New action button on that object, as the Visualforce page renders only first time, and then it always renders as blank page (total white page).
We checked from Browser's Console and verified if the Visualforce page exist in DOM, and found that the iFrame hosting the page does exist but BODY of the iFrame is totally empty.
I know this falls into a development related stuff and Salesforce would simply close down the support case, so I'm here asking if anyone else has been experiencing the same behavior?
Visualforce Page code to reproduce the Bug:
<apex:page standardController="Account">
<apex:form id="frmAccount" >
<apex:pageBlock title="Account Summary">
<apex:pageBlockSection columns="1">
<apex:inputField value="{!Account.Name}"/>
<apex:inputField value="{!Account.Phone}"/>
<apex:inputField value="{!Account.Industry}"/>
<apex:inputField value="{!Account.AnnualRevenue}"/>
</apex:pageBlockSection>
<apex:pageBlockButtons >
<apex:commandButton action="{!save}" value="Save"/>
<apex:commandButton action="{!cancel}" value="cancel"/>
</apex:pageBlockButtons>
</apex:pageBlock>
</apex:form>
</apex:page>
Steps to reproduce the bug:
- Create a
Visualforce Page
(use code above) - Set the
Visualforce Page
asNew
action button override on theAccount
object - Test within Lightning Experience environment
- Go to
Accounts
tab - Click
New
button. - When the Visualforce opens up, click
Cancel
button. - It will take you back to Accounts tab.
- Click
New
button again. - It will again open the Visualforce Page, but it will be rendered as a blank page.
- Either refresh the browser or logout/login and repeat steps #4 to #9.
==========================
UPDATE: Salesforce Support confirmed the bug (known issue link is still awaited), but the issue is currently being deployed in phases to instances, the platform version 228.11.1 patch release is supposedly being deployed with this specific issue to all users.