IOS App use awss3 synchronous show error "XMLParserError: Non-whitespace before first tag"

[alexxux]

Environment

Joplin version: 10.7.2
Platform: iPhone12
OS specifics: IOS14.3

Steps to reproduce

1.Import data from evernote
2. window use awss3 to sync
3. open e2ee
4. iphone complete synchronization
5. iphone input e2ee password start decryption
6. show the error message：“XMLParserError: Non-whitespace before first tag.”

Logfile

[JabinGP]

Same problem in my iPhone12mini and iPhone7.

[vbuser2004]

Experiencing a similar issue: Created notes on IOS. Sync'd fine at first to s3 (e2ee already enabled), but then it failed at some point (some notes were partially completed upon sync with PC).

Failure caused IOS app not to sync at all (in either direction), showing error below.

Was able to get it working by updating a note on my PC and sync'ing this to s3. Then, when syncing again on IOS, everything worked. This duplicates the remote (PC) entry however on IOS.

However, after editing in IOS again, the issue re-appears. Can get it working again by doing the above, with the same duplication issue.

XMLParserError: Non-whitespace before first tag. 
Line: 0
Column: 1
Char: i

[smcalilly]

I'm getting the same error with an iPhone SE. The encrypted notes successfully synced once, and now I can't sync the new notes that I've created on my desktop. The phone shows the same error as @alexxux.

[Jesssullivan]

Thanks @smcalilly & @alexxux, I am also seeing this error.

Reproduced in iOS simulator, I'll try to poke around and explore this bug this afternoon.

[idealclover]

Hello~any updates here?

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[root-io]

#4810

[zxkmm]

Hi! I got this error too on my iPhone 11 and ipad 8.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[zxkmm]

#4810 Some progress here.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

[raygervais]

Hello fellow note takers and developers!

Loving Joplin so far, but wanted to confirm that this issue has popped up for me as well when syncing to AWS S3. How far are we from an iOS release which includes the bugfix above? Thanks again for all the hard work! Hoping to contribute in the future as well.

[Tombert]

@raygervais For what it's worth, I found a workaround to get the iOS app working again after the that XML error happens.

If you go to the configuration, and change the sync target to somewhere else than S3, synchronize with that service, then once it's done, change back to S3 and resynchronize there.

[raygervais]

Thanks for the suggestion @Tombert, sadly the workaround doesn't appear to work in my case. Same error

[scottharwell]

@raygervais I know this will be a pain, but removing the app from both my iOS devices, then reinstalling and reconfiguring the S3 sync, then applying the encryption key password got me past the issue on my end.

[mweitzel2005]

@scottharwell that worked for me too.

NB: Anybody following this approach, bear in mind though that you potentially lose content created on the iOS device that hasn't been successfully sync'ed yet.

[crs1138]

Uff, I think I might have to ditch Joplin. Too grave of an error, too long no fix. 😞 It looked so promising.

[raygervais]

I ended up doing the same when Joplin didn't sync and notes I expected to have on my mobile for a meeting weren't there. Still love Joplin for local-based note taking, but can't leverage it for cloud sync via AWS just yet.

[dparker18]

@raygervais @crs1138 I'm curious to what?
I also really like the project and want to stick with it but a couple issues like this make it very difficult to justify

[raygervais]

@dparker18 So I've been leveraging Standard Notes happily since 2019, and wanted to move to Joplin for more of a Zettlekesten style of writing (aka Roam, Backlinks). Looks like I'll return to Standard Notes which hadn't let me down yet, just didn't have some of the features I was curious to try.

[crs1138]

@dparker18 - in the end I paid for Joplin's cloud… still not quite sure about that. If only Evernote had markdown support like Joplin and their app didn't take SOOOO long to start up.