Won't sync or display!

#1

I updated today, and suddenly I can’t display emails at all. Sync never finishes. This is what I see in red in my console:

UpdateAlertService started
main.7b7c3b6830b16ddbbc77.js:1 The “longpress” event cannot be bound because Hammer.JS is not loaded and no custom loader has been specified.
e.warn @ main.7b7c3b6830b16ddbbc77.js:1
main.7b7c3b6830b16ddbbc77.js:1 Applied appresizable
main.7b7c3b6830b16ddbbc77.js:1 Loading Xapian webassembly binary
main.7b7c3b6830b16ddbbc77.js:1 Applied appresizable
main.7b7c3b6830b16ddbbc77.js:1 Xapian boot time 1231 ms
3main.7b7c3b6830b16ddbbc77.js:1 Will navigate back to /
main.7b7c3b6830b16ddbbc77.js:1 ERROR Object
xt @ main.7b7c3b6830b16ddbbc77.js:1
main.7b7c3b6830b16ddbbc77.js:1 ERROR TypeError: Cannot read property ‘length’ of undefined
at an (main.7b7c3b6830b16ddbbc77.js:1)
at main.7b7c3b6830b16ddbbc77.js:1
at t.project (main.7b7c3b6830b16ddbbc77.js:1)
at t._next (main.7b7c3b6830b16ddbbc77.js:1)
at t.next (main.7b7c3b6830b16ddbbc77.js:1)
at t._next (main.7b7c3b6830b16ddbbc77.js:1)
at t.next (main.7b7c3b6830b16ddbbc77.js:1)
at XMLHttpRequest.o (main.7b7c3b6830b16ddbbc77.js:1)
at e.invokeTask (polyfills.c5db35788c3039a3ca30.js:1)
at Object.onInvokeTask (main.7b7c3b6830b16ddbbc77.js:1)
xt @ main.7b7c3b6830b16ddbbc77.js:1
main.7b7c3b6830b16ddbbc77.js:1 ERROR Object
xt @ main.7b7c3b6830b16ddbbc77.js:1
main.7b7c3b6830b16ddbbc77.js:1 ERROR Object
xt @ main.7b7c3b6830b16ddbbc77.js:1
main.7b7c3b6830b16ddbbc77.js:1 Will navigate back to /
main.7b7c3b6830b16ddbbc77.js:1 ERROR Object
xt @ main.7b7c3b6830b16ddbbc77.js:1
9main.7b7c3b6830b16ddbbc77.js:1 checking for updates
2main.7b7c3b6830b16ddbbc77.js:1 Applied appresizable
main.7b7c3b6830b16ddbbc77.js:1 ERROR DOMException
xt @ main.7b7c3b6830b16ddbbc77.js:1
11main.7b7c3b6830b16ddbbc77.js:1 checking for updates
runbox.com/:1 Unchecked runtime.lastError: The message port closed before a response was received.
3main.7b7c3b6830b16ddbbc77.js:1 checking for updates
main.7b7c3b6830b16ddbbc77.js:1 ERROR TypeError: Arguments to path.resolve must be strings
at Object.resolve (xapianasm.js:1)
at Object.lookupPath (xapianasm.js:1)
at Object.mknod (xapianasm.js:1)
at Object.mkdir (xapianasm.js:1)
at t._next (main.7b7c3b6830b16ddbbc77.js:1)
at t.__tryOrUnsub (main.7b7c3b6830b16ddbbc77.js:1)
at t.next (main.7b7c3b6830b16ddbbc77.js:1)
at t._next (main.7b7c3b6830b16ddbbc77.js:1)
at t.next (main.7b7c3b6830b16ddbbc77.js:1)
at t.notifyNext (main.7b7c3b6830b16ddbbc77.js:1)

Thanks.
D.

#2

Looks like you never got a response to this issue?

Since Runbox7 is in beta, there’s going to be frequent changes to the code, using a Private/Incognito window will give you the best experience without having to clear your cache frequently. Unless they have a robust cache-busting mechanism in place already. That hash in the filenames does appear to be one such tactic, so maybe the cache isn’t the issue.

Is this resolved for you?

1 Like
#3

Hi @davidjj,

The error you posted may indicate a problem connecting to the server or another connection issue.

If it happens again, can you try to reload the app and see if that helps?

– Geir