-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[iOS 15.3] Application immediatly close on sync with s3 target #6089
Comments
I’ve found error exception with iPhone connected to my Mac :
|
Hi! I'm on 15.2.1 now with the latest joplin app (12.6.2) and not getting this error. I also wrote the updated S3 code in Joplin.
|
Hello! I'm on iOS 15.3 now with the same lastest joplin app(12.6.2) and have the same error. My S3 backend is build with minio. By the way, on my MacOS 12.0.1 with joplin 2.5.12 and my Android 11 with joplin 2.3.4, this sync method is all OK.
|
Hi,
I'm on 41 too
Yes region is defined
Force path style is on
Yes I've done sync test with ok result and this no close app crash. |
Thanks, I'll see if I can repro in a test env. Can you add [iOS] -> [iOS 15.3] to the title for clarity? |
I attempted to test this tonight but I need a full OS update to get to the 15.3 simulator... I won't be able to get to that until at least next weekend. :( |
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. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information. |
I have the same issue with latest Joplin version on iOS. |
I was trying to migrate from Joplin server (self hosted) to S3 (also self hosted), but got the same result :
My config :
It doesn't seem to be linked to the iOS version as OP reported this on iOS 15.3. Also, the desktop app on my Mac sync correctly to this same S3 bucket. Some more info :
For now I just reverted to using my sefl hosted Joplin server. I was doing this for educational purpose. Let me know how I can help. |
I think this is a problem with something we send and what MinIO expects/returns Can you get logs from the minIO side and see if we can see the requests it received? Is your minio server by chance internet accessible that you could get me a test user set up? I suspect it's the same as #6047 |
Well I checked the trace logs of MinIO but I don't see any errors. I haven't found YET how to export these logs in text format, so are are some screenshot of what happens when I launch the app on my iPhone : Maybe there's a way to have more advanced logs... I'll have to investigate. My MinIO server is not exposed to the outside, but I can send you a temporary access so you can check by yourself. The connection goes to a reverse proxy though, but the result is the same : even when I try locally by configuring the S3 URL directly using a local ip (192.168.1.xxx) Joplin also crash, so I don't think it's linked to the reverse proxy |
Let me know how I can send you the S3 bucket configuration so you can try by yourself ;) |
@lbalogh find dot creativity at github username dot com -- i don't expect to have a chance to look at this until this weekend as I don't have a recent dev env set up. |
No problem. I sent you the information for the test S3 bucket so you can reproduce the crash. Note that as you won't be able to test it before the week-end, I'll only enable access from outside at the end of the week. Tell me if you need it before |
the latest joplin app on ios still crashed when sync with s3 (minio) |
@chaosye0 -- Any more insight? Logs? anything? |
app closes immediately when s3 sync started, and left one .locks folder in my joplin bucket. After I deleted the .locks folder, the windows joplin app then sync without error. |
Hi there! I've got same problem with my s3 minio instance. Here is a console logs from my iPhone12 |
Thanks! Any chance you have corresponding s3 minio logs as well for that time period? specifically say 5 minutes before and after this:
Basically in the logs before this I see an SSL connection being attempted, it appears to abort (posibly normal, maybe wrong ciphers) I see another SSL attemption connected, similar messages, and then I see a string of 200 requests, and then this 204 with an exception saying "client is gone". I think Minio logs would help to see what minio was doing with the connection and why. Beyond that, if you have a test bucket you can set up in minio without https I might suggest trying to sync that and see if the behavior is the same or different. I'm not sure if this is a "malformed request" that minio doesn't like or "SSL issues" that minio doesn't like. |
This is also happening to me when using third-party S3 providers like iDrive. Does there exist any temp workaround to run Joplin on iOS while this is addressed? Thanks |
Hi there! Sorry for delay. This log from minio(mc admin trace myminio -a -v). It all starts with launching the Joplin application on my iPhone. |
The sync process to S3 bucket cause an application close on iOS.
When S3 synchronization is configured, at sync process start, the application immediatly close. Even at application restart.
The issue stay in place after an application full uninstall/reinstall.
Tested with S3 target on AWS, Scaleway or Minio (through reverse proxy or not)
Environment
Joplin version: 12.6.2
Platform: iOS
OS specifics: iPhone 12 - iOS 15.3 (problem started on 15.2)
Steps to reproduce
Describe what you expected to happen
It’s expected to synchronization ran normally without application close
Logfile
No relevant log available on iPhone, and no relevant log with minio target (no minio server relevant log)
The text was updated successfully, but these errors were encountered: