The passport expiry date field not showing up on the OCI profile update portal is a recurring issue we handle weekly; it’s almost always a client-side rendering problem, not a fundamental flaw in your application.
This specific glitch stops a straightforward update process cold, leaving users unable to complete a mandatory governmental requirement.
People search for this because they are stuck, blocked from finalizing their OCI update after renewing their passport, and are worried about compliance.
We are going to walk through the exact steps to diagnose and fix this, covering the technical reasons it happens and the practical workarounds we use every day to get applications moving.
Troubleshooting Missing Passport Expiry Date
Browser and Cache Issues
The most common issue is your web browser. Over the years, we've seen government portals like this one behave unpredictably with different browsers or even different versions of the same browser. The code that displays the form fields can fail to load correctly.
Your first action should always be a hard refresh. On most browsers, this is done by pressing Ctrl+F5 (on Windows) or Cmd+Shift+R (on Mac). This forces the browser to download the latest version of the page from the server, ignoring any cached, potentially broken files. If that fails, the next step is to clear your browser's cache and cookies completely. This data can sometimes corrupt how a page is displayed. After clearing, close the browser, reopen it, and log in again.
Also Read-
Can OCI Cardholders Buy Property in India?
Trying a Different Browser
If a hard refresh and cache clearing don't work, the next logical step is to switch browsers. The
OCI portal was built using older web technologies that sometimes have compatibility issues with modern browsers.
We find that what fails in Chrome might work perfectly in
Mozilla Firefox or Microsoft Edge, and vice versa. It’s a simple test that costs nothing and has a surprisingly high success rate. Don't just open a new tab; close the problematic browser entirely and start a fresh session in a different one. This ensures no session data carries over.
The "Start Over" Method
Sometimes, the session itself becomes corrupted on the server side. You might have timed out, or a previous action might have put your application into a strange state. The only way to fix this is to abandon the current attempt. Log out of the portal completely. Close your browser.
Wait for about 15-20 minutes to ensure the server-side session fully expires. Then, open your browser and begin the process from the very beginning. We've seen this simple "wait and restart" approach resolve countless cases where form fields, including the passport expiry date, mysteriously vanish.
Inspecting Page Elements
For those with a bit more technical confidence, you can use your browser's developer tools. Right-click on the area where the field should be and select "Inspect" or "Inspect Element." This opens a panel showing the website's code.
Look for a form field related to the expiry date that might be hidden (e.g., `style="display:none;"`). While you can't permanently change the code, seeing a hidden field confirms it's a display issue on your end, reinforcing the need to try the browser-based solutions mentioned above. It tells you the problem isn't with your OCI record itself.
Our suggestion
Don't just click buttons; work the system. We've found that sometimes the portal's internal logic needs a nudge. Try navigating away from the passport details section to another section (like address details) and then navigating back. This action can force the page to re-render its components, often causing the missing field to appear. It's like resetting the form without resetting your entire session.
Another move is to re-select the document type you are updating. Even if "New Passport" is already selected, click the dropdown menu and select it again. This can trigger a script on the page that is supposed to show the relevant fields, including the passport expiry date. We see this work when the page loads in a partially incorrect state. It's a small action, but it often resets the page's dynamic logic.
Comments