Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync failure on iOS app for some notes #3986

Closed
TheOtherGuy opened this issue Oct 26, 2020 · 1 comment
Closed

Sync failure on iOS app for some notes #3986

TheOtherGuy opened this issue Oct 26, 2020 · 1 comment
Labels
backlog We'll get to it... eventually... bug It's a bug iOS

Comments

@TheOtherGuy
Copy link

I have a saved complete page (HTML) from a website which can save with no issues on desktop Joplin, but when I tried to sync using iOS Joplin, it will throw an error. It seems that the Wordpress code is causing some issue? I tried deleting the note and then resaving the page, but the same error occurs. Sync is done via Windows OneDrive.

Environment

Joplin version: 10.2.1
Platform: iOS
OS specifics: iOS 13.5

Steps to reproduce

  1. Save this webpage as a complete HTML page via Joplin clipper. There are a few other webpages which has similar issues.
  2. It can be synced successfully on Windows Joplin.
  3. Sync will fail on iOS Joplin.

Describe what you expected to happen

Successful sync across platforms.

Logfile

As attached.
Joplin iOS Logfile
joplin iOS error message

@TheOtherGuy TheOtherGuy added the bug It's a bug label Oct 26, 2020
@laurent22 laurent22 added high High priority issues iOS labels Oct 26, 2020
@laurent22
Copy link
Owner

Looks like the sync issue cannot be fixed as it is a bug in the network library we use. Specifically the React Native fetch() function will truncate strings that contain binary data (That binary data shouldn't be there but due to a bug in the clipper it was)

I'll keep the JEX file here anyway in case that bug is fixed some day so that it can be tested again:

BROKEN JEX FILE

As I'm not sure the JEX file will preserve the broken encoding, here it is directly from the sync target:

984d0978d5684284b583ef121d058fe0.zip

I will however fix the issue that generated the invalid file in the first place.

@laurent22 laurent22 added backlog We'll get to it... eventually... and removed high High priority issues labels Oct 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog We'll get to it... eventually... bug It's a bug iOS
Projects
None yet
Development

No branches or pull requests

2 participants