Bug #2882
App does not load on iOS Safari: old chunks are being referred to
Status:
Closed
Priority:
Immediate
Assignee:
-
Target version:
-
Start date:
01/15/2022
Due date:
% Done:
0%
History
#1
Updated by Luke Murphey over 2 years ago
Updated by - Subject changed from App does not load on iOS Safati to App does not load on iOS Safari
#2
Updated by Luke Murphey over 2 years ago
Questions:
- Does it work on other devices?
- It works on my phone
- Dose it work on desktop Safari?
- What is the error?
- The error is "Minified React error #306"
- https://reactjs.org/docs/error-decoder.html/?invariant=306
- Does it work in private mode?
- Yes
- It does load on Chrome on the same device
- https://stackoverflow.com/questions/64367591/react-app-not-working-in-safari-working-fine-on-chrome-and-firefox-but-giving-b
- https://github.com/fuse-box/fuse-box/issues/1646
- https://www.geeksforgeeks.org/how-to-clear-complete-cache-data-in-reactjs/
- https://stackoverflow.com/questions/58475780/react-apollo-error-invariant-violation-could-not-find-client-in-the-context
#3
Updated by Luke Murphey about 2 years ago
This is likely due to lazy loading. The main page is trying to load the older chunks.
#4
Updated by Luke Murphey about 2 years ago
- Subject changed from App does not load on iOS Safari to App does not load on iOS Safari: old chunks are being referred to.
#5
Updated by Luke Murphey about 2 years ago
- Subject changed from App does not load on iOS Safari: old chunks are being referred to. to App does not load on iOS Safari: old chunks are being referred to
- Target version set to 4.7.3
#7
Updated by Luke Murphey about 2 years ago
Solution:
- "it’s also a good idea to have your index.html and entrypoint files never cached, which can be done using the cache-control header (Cache-Control - HTTP | MDN)"
#9
Updated by Luke Murphey 12 months ago
- Status changed from New to Closed
- Target version deleted (
4.7.3)