laurent22 / joplin

Joplin - the privacy-focused note taking app with sync capabilities for Windows, macOS, Linux, Android and iOS.
https://joplinapp.org
Other
46.12k stars 5.02k forks source link

Blank screen on share, subsequent shares not saved #10850

Open Terrance opened 3 months ago

Terrance commented 3 months ago

Operating system

Android

Joplin version

3.0.7

Desktop version info

Not desktop, but the Android debug info for reference:

Joplin 3.0.7 (prod, android)

Client ID: d8e98c66054049f0b59e6d8c0db590b2
Sync Version: 3
Profile Version: 47
Keychain Supported: No

Joplin Calendar: 1.2.0
Outline: 1.5.13

Android API level: 33
WebView version: 127.0.6533.66
WebView package: com.google.android.webview
FTS enabled: 1
Hermes enabled: 1

Current behaviour

Expected behaviour

Incoming shared content to be recognised and persisted consistently.

Logs

📎 syncReport-1723220079287-snip.txt

Possible exception of interest:

08-09T17:11:55,20,"AsyncActionQueue: Unhandled error: TypeError: right operand of 'in' is not an object
TypeError: right operand of 'in' is not an object
    at diffObjectsFields (address at index.android.bundle:1:1716431)
    at ?anon_0_ (address at index.android.bundle:1:5990985)
    at next (native)
    at fulfilled (address at index.android.bundle:1:5989858)
    at tryCallOne (address at InternalBytecode.js:1:1180)
    at anonymous (address at InternalBytecode.js:1:1874)
    at apply (native)
    at anonymous (address at index.android.bundle:1:286591)
    at _callTimer (address at index.android.bundle:1:285542)
    at _callReactNativeMicrotasksPass (address at index.android.bundle:1:285686)
    at callReactNativeMicrotasks (address at index.android.bundle:1:287676)
    at __callReactNativeMicrotasks (address at index.android.bundle:1:148328)
    at anonymous (address at index.android.bundle:1:147412)
    at __guard (address at index.android.bundle:1:148166)
    at flushedQueue (address at index.android.bundle:1:147323)
    at invokeCallbackAndReturnFlushedQueue (address at index.android.bundle:1:147266)"

Note that this log contains a number of sync errors due to not being on my local network -- I don't believe this to be relevant as I've also seen this issue at home with sync available.

This failure mode has so far only happened a couple of times since 3.0, and does not seem to be readily reproducible.

pedromj commented 2 months ago

I have seen this behavior for some time. I thought it was related to my particular settings. I see it is more general now.