Stack Overflow error when trying to Sync

[Brian2-Cohen-Bose]

I am now getting constant Stack Overflow errors when trying to sync between Safari on iOS and Chrome on Mac. @talex5, Is there debug logs I can post here to help your troubleshoot?

[Brian2-Cohen-Bose]

@talex5 I get myself out this by removing my cuekeeper/ directory, re-cloning master, and building the client and server. Right now, between my phone and laptop, the sync'ing is working fine right now. Some thoughts:

• When I originally setup the server, I only had one entry in the devices.ml file that I was using for both my phone and laptop. Then when I ran into the sync issues, I added an additional device, but that did not resolve it. This time, I have different sha256 for each device ( which I know that what I'm supposed to do). Not sure if this caused the sync/stack overflow issues.
• unrelated to the stack overflow issue, when I did the above steps, my data was still there! Where the heck is the data stored? Not in the cuekeeper/ dir (obviously)?

[Brian2-Cohen-Bose]

Well, back to getting the stack overflow messages on Safari iOS now (syncing to my Mac cuekeeper server on my local network). Would love to help debug this @talex5 with guidance...let me know.

[talex5]

A stack overflow where? On iOS? On Chrome? On the server?

The server doesn't store the data on disk at all at the moment. It's all stored in the browser, and the browser sends to whole history to the server the first time it connects after the server restarts.

The only stack-overflow issue I know about is https://github.com/talex5/cuekeeper/issues/2. However, it's quite unlikely you'd trigger that in real use. If you did get that, just refreshing the browser tab would fix it.

[Brian2-Cohen-Bose]

Stack overflow errors on both Mac Chrome and iOS Chrome or Safari. When I click the Sync button, getting Stack Overflow errors.
A browser refresh clears the red overflow banner, but then it comes back.

I have deleted cuekeeper and rebuilt several times, but after a few syncs start to hit this issue again. Maybe I can clear by client/browser side data? How do I do that? Not sure where to find it.