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

Dropbox sync occasionally returns 504 error on iOS devices #645

Open
reinhart1010 opened this issue Nov 3, 2020 · 42 comments
Open

Dropbox sync occasionally returns 504 error on iOS devices #645

reinhart1010 opened this issue Nov 3, 2020 · 42 comments

Comments

@reinhart1010
Copy link

reinhart1010 commented Nov 3, 2020

Your Environment

  • Version used: 6.0.1, Web
  • Operating System and version: iOS 14.1
  • Desktop Environment:
  • Browser Name and version: Safari 14.1

Expected Behavior

The Dropbox sync should work fine. I have tested this against the web app on Android (not the ones downloaded from Play Store)

Current Behavior

The app returns Unknown Sync Error: Error: Request failed with Status 504.

Steps to Reproduce (for bugs)

  1. Open the web app on Safari
  2. Add to Home Screen
  3. Go to the app Settings (in PWA) to set up Dropbox sync
  4. Try wait for 30 mins to 1 hour and try to synchronize again

Console Output

Unfortunately, in order to get the console output I need to connect to a Mac device, which I don't have.

Error Log (Desktop only)

Screenshot

image

@reinhart1010
Copy link
Author

Update: This issue seems to only occur when the app wants to update the data from the Dropbox server (Remote). Otherwise, it will work normally

@johannesjo
Copy link
Owner

johannesjo commented Nov 3, 2020

Hi there! Thanks for digging into this. Does this happen a 100% of time when data is being loaded? Or just sometimes?

EDIT: Well the title says it all. Sorry!

@reinhart1010
Copy link
Author

reinhart1010 commented Nov 4, 2020 via email

1 similar comment
@reinhart1010
Copy link
Author

  1. When the app is first launched, as long as there are no remote changes, the sync works fine.
  2. Otherwise, the error will occur indefinitely.

I also suspect that this also affects the Google Drive sync functionality, as I have experience an "Unknown Sync Error: [Object object]" when syncing with Google Drive on iOS, while it does not occur in the web app on Android (I didn't use the native app due to #434).

@johannesjo
Copy link
Owner

I tried to reproduce this on Mac OS as I don't have an iPhone available to debug this. Unfortunately, I was unable to do so.

I opened up an issue here:
https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/504-when-reading-data/m-p/467507#M23844

I hope they can help us.

@johannesjo
Copy link
Owner

A fix for this should be out with the next release and is ready for testing under https://test-app.super-productivity.com/

Could you maybe check there if the problem still occurs?

@reinhart1010
Copy link
Author

I am currently planning to test the staging app but it seems there is another layout issue.

image

@johannesjo
Copy link
Owner

@reinhart1010 should be fixed now.

@reinhart1010
Copy link
Author

reinhart1010 commented Nov 24, 2020

The layout issue is still reproducible from test-app.super-productivity.com, while the main app.super-productivity.com does not. Already tried resetting the site data from Safari settings.

@johannesjo
Copy link
Owner

Thanks @reinhart1010 at this point the app.super-productivity.com version might have been the more up to date one. I just updated the test... version as well.

@reinhart1010
Copy link
Author

I have already tested in 6.1.1 and the issue still persists.

@johannesjo
Copy link
Owner

I have already tested in 6.1.1 and the issue still persists.

the styling issue or the 504 error or both?

@reinhart1010
Copy link
Author

The styling issue has been fixed. The 504 error still persists.

@reinhart1010
Copy link
Author

Upgrading to 6.1.2 and the issue seems have been fixed. I'll be testing a few more times before closing it as fixed.

@reinhart1010
Copy link
Author

reinhart1010 commented Dec 4, 2020

However it still fails with 504 (I guess this is still related to the Service Worker). Trying to reconnect after Airplane Mode does not work as well.

@johannesjo
Copy link
Owner

May I ask what version is shown when you navigate to the settings on the mobile app?

@reinhart1010
Copy link
Author

![Uploading 101236424...]

@johannesjo
Copy link
Owner

![Uploading 101236424...]

Seems like something went wrong.

@reinhart1010
Copy link
Author

image

@johannesjo
Copy link
Owner

Thank you! I tested with a mac book air safari and I am able to reproduce this as well. I know what is causing this (the service worker stuff still seems to be active for mac somehow), but I don't have a fix yet.

@github-actions
Copy link

github-actions bot commented Mar 7, 2021

This issue has not received any updates in 90 days. Please comment, if this still relevant!

@reinhart1010
Copy link
Author

So it seems this is a duplicate of angular/angular#37133

@johannesjo johannesjo removed the Stale label Jul 21, 2021
@WantToLearnJapanese
Copy link

WantToLearnJapanese commented Aug 30, 2021

This issue happens also on macOS-Safari.

There is a weird behavior with this issue.

For the first sync (use remote), there is no problem.

@WantToLearnJapanese
Copy link

Just as a workaround, on iOS, we can use "Alook" which do not suffer from the issue. (This is a paid app $0.99)

I am very curious about why Alook works. Aren't all the browsers on iOS just Safari with different skin?

@WantToLearnJapanese
Copy link

@johannesjo Isn't it weird that there is no problem for the first sync?

@johannesjo
Copy link
Owner

@johannesjo Isn't it weird that there is no problem for the first sync?

Yes, this might have something to do with some caching going on maybe.

@github-actions
Copy link

github-actions bot commented Jan 2, 2022

This issue has not received any updates in 90 days. Please comment, if this still relevant!

@ribtoks
Copy link

ribtoks commented Feb 12, 2022

This issue still persists as of today in the web app on latest iPadOS with latest Safari

@johannesjo johannesjo reopened this Feb 12, 2022
@johannesjo johannesjo removed the Stale label Feb 12, 2022
@johannesjo
Copy link
Owner

Help with this would be welcome! I currently have no iOS devices available to check this.

@m4nured
Copy link

m4nured commented May 28, 2022

Hi Johannes,
What kind of iOS device do you need for checking?
I am thinking about supporting this awesome project by sending you a functional iOS-device.
Would be an iPhone 6s which runs the latest iOS but has a non-essential defect okay, like stripes on the display or some other. Then I might look for a device on "Kleinanzeigen" in the next weeks.
Sebastian.

@johannesjo
Copy link
Owner

Hey @m4nured ! This is incredibly kind of you! :) Thank you very much for the offer! It would possibly be very helpful for debugging IOS related issues and an older iphone sounds perfect for the task. If you still would be willing to go down with this (I totally understand if you don't), we can discuss this via email (contact@super-productivity.com).

@github-actions
Copy link

github-actions bot commented Oct 5, 2022

This issue has not received any updates in 90 days. Please comment, if this still relevant!

@github-actions github-actions bot added the Stale label Oct 5, 2022
@MikeMorenoDSP
Copy link

Also getting this issue (504)
iPhone 12 running iOS 15.5 using Safari and Dropbox.
Going to test if there are more alternatives than "Alook Browser".

@github-actions github-actions bot removed the Stale label Oct 6, 2022
@eclecticpassions
Copy link

I’m on iPad OS 16.1.1, SP 7.12.0, syncing using Dropbox and created an App Shortcut via Safari to quickly access the app via the home screen. Also have the error code: Unknown sync error. Error: Request failed with status code 504. It also works on the first time, but subsequently fails unless I delete all the cache files in Safari settings related to superproductivity.com and restart Safari. Syncing to Dropbox via my Mac OS Catalina and on Android 12 is okay so far.

@michaellammers
Copy link

Having the same problem, but mainly here to thank you for this great tool. Been in a week and already loving it!

@eclecticpassions
Copy link

Can confirm A Look Browser works flawlessly on my ipad mini 6.

@tiropictor
Copy link

tiropictor commented May 8, 2023

can confirm that error is still here, iPad Air 4th gen, iOS 16.2 (20C65), using default browser for PWA added to homescreen, getting "Unknown Sync Error: Error: Request failed with status code 504"

(Super Productivity v7.13.2)

Other two devices (Android, using app from f-Droid, and Mac, using mac app downloaded from GitHub) sync perfectly.

@ITCMA
Copy link

ITCMA commented Jun 11, 2023

Can also confirm error "Unknown Sync Error: Error: Request failed with status code 504" on iOS 16.5 with iPhone 14 Pro and iPad Gen 8. Tested with Chrome, Safari and Firefox Browser. Super Productivity Version v7.13.2.

macOS Ventura (App Store Version - not the Browser) syncing without any problem. If i try it with Chrome on macOS i see the same error 504.

iOS Console for Chrome:

standard	13:19:07.586795+0200	Chrome	Evaluating dispatch of UIEvent: 0x280ecdee0; type: 0; subtype: 0; backing type: 11; shouldSend: 1; ignoreInteractionEvents: 0, systemGestureStateChange: 0
standard	13:19:07.587423+0200	Chrome	Sending UIEvent type: 0; subtype: 0; to windows: 1
standard	13:19:07.587930+0200	Chrome	Sending UIEvent type: 0; subtype: 0; to window: <ChromeOverlayWindow: 0x108b0b670>; contextId: 0x95877E37
standard	13:19:07.604664+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState: type=2
standard	13:19:07.604687+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState(Foreground) Taking foreground assertion for network process
standard	13:19:07.604712+0200	Chrome	0x117018390 - [PID=4416, throttler=0x11800ba40] ProcessThrottler::Activity::Activity: Starting foreground activity / 'WebPageProxy::runJavaScriptInFrameInScriptWorld'
standard	13:19:07.604736+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState: type=2
standard	13:19:07.604760+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState(Foreground) Taking foreground assertion for network process
standard	13:19:07.605942+0200	Chrome	Evaluating dispatch of UIEvent: 0x280ecdee0; type: 0; subtype: 0; backing type: 11; shouldSend: 0; ignoreInteractionEvents: 0, systemGestureStateChange: 0
standard	13:19:07.605990+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.606021+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.606057+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.606086+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.617122+0200	Chrome	0x117018390 - [PID=4416, throttler=0x11800ba40] ProcessThrottler::Activity::invalidate: Ending foreground activity / 'WebPageProxy::runJavaScriptInFrameInScriptWorld'
standard	13:19:07.617161+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState: type=2
standard	13:19:07.617217+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState(Foreground) Taking foreground assertion for network process
standard	13:19:07.617243+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState: type=2
standard	13:19:07.617266+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState(Foreground) Taking foreground assertion for network process
standard	13:19:07.617290+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.617312+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.617336+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.617358+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.649384+0200	Chrome	Evaluating dispatch of UIEvent: 0x280ecdee0; type: 0; subtype: 0; backing type: 11; shouldSend: 1; ignoreInteractionEvents: 0, systemGestureStateChange: 0
standard	13:19:07.649430+0200	Chrome	Sending UIEvent type: 0; subtype: 0; to windows: 1
standard	13:19:07.649589+0200	Chrome	Sending UIEvent type: 0; subtype: 0; to window: <ChromeOverlayWindow: 0x108b0b670>; contextId: 0x95877E37
standard	13:19:07.650834+0200	Chrome	Single tap identified. Request details on potential zoom. (0x10a0ab800, pageProxyID=82)
standard	13:19:07.650860+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState: type=2
standard	13:19:07.650882+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState(Foreground) Taking foreground assertion for network process
standard	13:19:07.652354+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.652409+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.652452+0200	Chrome	Potential tap may cause significant zoom. Wait. (0x10a0ab800, pageProxyID=82)
standard	13:19:07.652782+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState: type=2
standard	13:19:07.652821+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::didChangeThrottleState(Foreground) Taking foreground assertion for network process
standard	13:19:07.652911+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.652950+0200	Chrome	0x11800b8a0 - [PID=4416] WebProcessProxy::updateRemoteWorkerProcessAssertion: workerType=service
standard	13:19:07.653772+0200	Chrome	Ending potential tap. (0x10a0ab800, pageProxyID=82)
standard	13:19:07.653835+0200	Chrome	Single tap recognized - commit potential tap (0x10a0ab800, pageProxyID=82)
standard	13:19:07.665496+0200	Chrome	Synthetic click completed. (0x10a0ab800, pageProxyID=82)
standard	13:19:07.665927+0200	Chrome	Evaluating dispatch of UIEvent: 0x280ecdee0; type: 0; subtype: 0; backing type: 11; shouldSend: 0; ignoreInteractionEvents: 0, systemGestureStateChange: 1
standard	13:19:07.665967+0200	Chrome	Evaluating dispatch of UIEvent: 0x280ecdee0; type: 0; subtype: 0; backing type: 11; shouldSend: 0; ignoreInteractionEvents: 0, systemGestureStateChange: 0
standard	13:19:07.859735+0200	Chrome	<private>: Will add backgroundTask with taskName: <private>, expirationHandler: <__NSMallocBlock__: 0x283924570>
standard	13:19:07.859788+0200	Chrome	<private>: Creating new assertion because there is no existing background assertion.
standard	13:19:07.859838+0200	Chrome	<private>: Creating new background assertion
standard	13:19:07.859898+0200	Chrome	<private>: Created new background assertion <BKSProcessAssertion: 0x2814a1db0>
standard	13:19:07.861495+0200	Chrome	<private>: Incrementing reference count for background assertion <private>
standard	13:19:07.861632+0200	Chrome	<private>: Created background task <private>.
standard	13:19:07.861689+0200	Chrome	user sessions enabled, targeting 501
standard	13:19:07.865268+0200	Chrome	cleaning up unpooled xpc conn to trustd 0x280ce9a40
standard	13:19:07.865354+0200	Chrome	got event: Connection invalid
standard	13:19:07.865520+0200	Chrome	<private>: Ending background task with UIBackgroundTaskIdentifier: 1824
standard	13:19:07.865617+0200	Chrome	<private>: Ending task with identifier 1824 and description: <private>, _expireHandler: <__NSMallocBlock__: 0x283924570>
standard	13:19:07.865778+0200	Chrome	<private>: Decrementing reference count for assertion <private> (used by background task with identifier 1824: <private>)
standard	13:19:07.865823+0200	Chrome	<private>: Will invalidate assertion: <BKSProcessAssertion: 0x2814a1db0> for task identifier: 1824

@github-actions
Copy link

This issue has not received any updates in 90 days. Please comment, if this still relevant!

@github-actions github-actions bot added the Stale label Oct 12, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2023
@jechogit
Copy link

I still have the same problem, my device is an Iphone 14 pro Max.

@edi-gr
Copy link

edi-gr commented Feb 7, 2024

Yes I’m having same issue, it worked the first time but now sync never works(all other features work fine)
It’s an amazing app but this bug is a real pain in the a**
I have an iPad 10th gen with 16.6 IpadOS

@johannesjo johannesjo reopened this Feb 9, 2024
@johannesjo johannesjo removed the Stale label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests