Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #56436 Back to Issue ]
Summary 0056436: blank page on 1st login after deploy
Revision 2024-09-12 10:34 by alostale
Steps To Reproduce 1. Prepare a new production version
1.1 For example apply the attached patch in core2 module modifying the "version" number. This number is displayed in login and in main screens so it's easy to know which is the current version.
1.2 Build and deploy the new version: run ant build.prod from mdoules/org.openbravo.core2 directory

2. Operate POS
2.1 Load login screen using production build (not development server), using the <context>/web/pos url
2.2 Log in
2.3 Close the POS browser's tab

3. Repeat steps defined in 1 (increasing version number)

4. Repeats steps defined in 2
4.1 Note in 2.1 the version number is n-1 (previous version) -> OK
4.2 On log in
  ERROR: blank screen
         Although it seems the new index.html has been requested, we somehow continue using the old one (n-1) that references to the old index-[n-1].js as it's been already removed from the resources cached by the service worker, it is tried to be fetched but it is not present anymore resulting on a 404.
         
Revision 2024-09-12 10:32 by alostale
Steps To Reproduce 1. Prepare a new production version
1.1 For example apply the attached patch modifying the "version" number. This number is displayed in login and in main screens so it's easy to know which is the current version.
1.2 Build and deploy the new version: run ant build.prod from mdoules/org.openbravo.core2 directory

2. Operate POS
2.1 Load login screen using production build (not development server), using the <context>/web/pos url
2.2 Log in
2.3 Close the POS browser's tab

3. Repeat steps defined in 1 (increasing version number)

4. Repeats steps defined in 2
4.1 Note in 2.1 the version number is n-1 (previous version) -> OK
4.2 On log in
  ERROR: blank screen
         Although it seems the new index.html has been requested, we somehow continue using the old one (n-1) that references to the old index-[n-1].js as it's been already removed from the resources cached by the service worker, it is tried to be fetched but it is not present anymore resulting on a 404.
         
Revision 2024-09-12 10:23 by alostale
Steps To Reproduce 1. Prepare a new production version
1.1 For example apply the attached patch modifying the "version" number. This number is displayed in login and in main screens so it's easy to know which is the current version.
1.2 Build and deploy the new version: run ant build.prod from mdoules/org.openbravo.core2 directory

2. Operate POS
2.1 Load login screen using production build (not development server), using the <context>/web/pos url
2.2 Log in
2.3 Close the POS browser's tab

3. Repeat steps defined in 1 (increasing version number)

4. Repeats steps defined in 2
4.1 Note in 2.1 the version number is n-1 (previous version) -> OK
4.2 On log in
  ERROR: blank screen
         Although it seems the new index.html has been requested, we somehow continue using the old one (n-1) that references to the old index.js as it's been already removed from the resources cached by the service worker, it is tried to be fetched but it is not present anymore.
         
Revision 2024-09-12 10:21 by alostale
Steps To Reproduce 1. Prepare a new production version
1.1 For example apply the attached patch modifying the "version" number. This number is displayed in login and in main screens so it's easy to know which is the current version.
1.2 Build and deploy the new version: run ant build.prod from mdoules/org.openbravo.core2 directory

2. Operate POS
2.1 Load login screen
2.2 Log in
2.3 Close the POS browser's tab

3. Repeat steps defined in 1 (increasing version number)

4. Repeats steps defined in 2
4.1 Note in 2.1 the version number is n-1 (previous version) -> OK
4.2 On log in
  ERROR: blank screen
         Although it seems the new index.html has been requested, we somehow continue using the old one (n-1) that references to the old index.js as it's been already removed from the resources cached by the service worker, it is tried to be fetched but it is not present anymore.
         


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker