DOES NOT PROCESS THE INFO
-
With the latest update, when placing fulfill the order, it remains processing without finishing.
-
Experiment add-an-image-to-pdf-with-alt-text-rollout has unknown featureId: addAnImageInPDF RemoteSettingsExperimentLoader.sys.mjs:709:21
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
Experiment tab-hover-preview-release-rollout has unknown featureId: tabPreview RemoteSettingsExperimentLoader.sys.mjs:709:21
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
TypeError: WindowGlobalParent.drawSnapshot: Argument 2 is not a finite floating-point value.
????drawSnapshot chrome://global/content/elements/browser-custom-element.js:1791
????captureTabPreviewThumbnail resource://gre/modules/PageThumbs.sys.mjs:535
tab-hover-preview.mjs:124:17
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
PushDB: update: Ignoring invalid update 53d37087-2baf-4322-ad50-7db7e2b12bd0 null PushDB.sys.mjs:413
PushService: receivedPushMessage: Error notifying app AbortError PushService.sys.mjs:813
El recurso en “https://csp.withgoogle.com/csp/gws/fff” fue bloqueado por OpaqueResponseBlocking. Razón: “nosniff is true and mimeType is an opaque-blocklisted MIME type or its essence is 'text/plain'”.Is it possible that the problem is with the carrier I used? I see that the logo is not displayed and they may not have updated the information. Correo Argentino is the carrier.
how fluid and well it works when I deactivate the El loco translator plugin, it’s fantastic! but unfortunately I need it!-
This reply was modified 5 months, 1 week ago by
maza25.
Please try syncing the shipping carriers to ensure the most up-to-date information is available.
You can follow this documentation to sync the shipping carriers: Sync the Shipping Providers.
I don’t think the issue is related to the carrier you’re using (Correo Argentino). It could be a conflict with the Loco Translate plugin, as you mentioned.
-
This reply was modified 5 months, 1 week ago by
- You must be logged in to reply to this topic.