[COMPASS-5502] Migration from 1.19.2 to 1.30.1 causes Compass to error on load Created: 09/Feb/22 Updated: 28/Jun/23 Resolved: 27/Mar/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | State Management, Tech debt |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rhys Howell | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS: |
||
| Attachments: |
|
| Documentation Changes: | Not Needed |
| Description |
|
Reported OS: windows Slack thread: Looks like what's probably happening is that in the 1.20 migration step the `storage mixin` is using the `localforage` package which throws an uncaught exception. We might be able to fix what causes localforage to throw the `No available storage method found` expection or just catch the exception so Compass is still usable without performing a full migration. Debug screenshots attached |