Hi Bhanu,
What you're seeing is usually related to how the browser remembers the last selected profile for an Offline Web app.
Since Offline Web uses service workers and local caching, I've seen situations where the browser continues loading the offline profile even when the device is online. This is especially noticeable after the app has been opened once in offline mode.
A few things I'd verify:
If your requirement is:
then a practical approach is similar to what Daniel described:
Plain Text
?profile=Responsive
I've used a similar pattern because profile selection isn't automatically switched once the Offline Web profile has loaded.
One additional test: deploy a very small page in the Responsive profile and navigate directly to:
Plain Text
https://<app-url>/?profile=Responsive
If that works consistently, then the issue is likely related to profile selection/caching rather than authentication or deployment.
Since it works locally but behaves differently in the cloud, I'd especially investigate service worker cache and stored profile selection in the browser before looking at the application logic itself.
Hope this helps.