bug: "Error loading profile."
frknltrk opened this issue · 7 comments
i'm having this issue occasionally when i open up the app. i can access the ui where the notes displayed only when i tap on the "Retry" a bunch of times.
I got this problem too today (Mon Nov 23 11:52:20 MSK 2020).
On deskop app and on androind.
In desktop app developer tools (cmd + shift + k) timeout error:
I'm trying to connect to the server from my local compiled desktop client and got these logs:
$ make run
./node_modules/.bin/electron .
2020-11-23T12:01:03 - [INFO][turtl_core] main::init() -- init with user config {"data_folder":"/Users/vaan/Library/Application Support/Turtl/core","api":{"client_version_string":"desktop/0.7.2-6","proxy":null},"openssl_cert_file":"/Users/vaan/sources/turtl/desktop/scripts/resources/cacert.pem"}
2020-11-23T12:01:03 - [INFO][turtl_core] main::init() -- created data folder: /Users/vaan/Library/Application Support/Turtl/core
2020-11-23T12:01:03 - [INFO][turtl_core] main::start() -- begin
2020-11-23T12:01:03 - [INFO][turtl_core] main::start() -- locking data dir: /Users/vaan/Library/Application Support/Turtl/core/run.lock
2020-11-23T12:01:03 - [INFO][turtl_core::messaging] messaging::start() -- main loop
2020-11-23T12:01:03 - [INFO][turtl_core::messaging] messaging::ui_event() -- messaging:ready
2020-11-23T12:01:03 - [INFO][turtl_core::dispatch] dispatch(1): app:api:set-config
2020-11-23T12:01:03 - [INFO][turtl_core::dispatch] dispatch(2): user:login-from-saved
2020-11-23T12:01:03 - [INFO][turtl_core::models::user] User::restore_login() -- restored login from "/Users/vaan/Library/Application Support/Turtl/core/36022.login"
2020-11-23T12:01:08 - [INFO][turtl_core::api] api::call() -- res(7): 200 POST https://apiv3.turtlapp.com/auth
2020-11-23T12:01:16 - [INFO][turtl_core::api] api::call() -- res(422): 200 GET https://apiv3.turtlapp.com/users/36022
2020-11-23T12:01:16 - [INFO][turtl_core::messaging] messaging::ui_event() -- user:login
2020-11-23T12:01:16 - [INFO][turtl_core::dispatch] dispatch(3): sync:start
2020-11-23T12:01:16 - [INFO][turtl_core::sync] sync::runner() -- outgoing init (run 1)
2020-11-23T12:01:16 - [INFO][turtl_core::sync] sync::runner() -- outgoing main loop
2020-11-23T12:01:16 - [INFO][turtl_core::sync] sync::runner() -- files:outgoing init (run 1)
2020-11-23T12:01:16 - [INFO][turtl_core::sync] sync::runner() -- incoming init (run 1)
2020-11-23T12:01:16 - [INFO][turtl_core::sync] sync::runner() -- files:incoming init (run 1)
2020-11-23T12:01:16 - [INFO][turtl_core::sync] sync::runner() -- files:outgoing main loop
2020-11-23T12:01:16 - [INFO][turtl_core::sync] sync::runner() -- files:incoming main loop
2020-11-23T12:01:26 - [ERROR][turtl_core::sync] sync::runner() -- incoming: init: {"message":"error sending request for url (https://apiv3.turtlapp.com/sync?sync_id=3094563&type=initial): operation timed out","type":"generic"}
2020-11-23T12:01:26 - [INFO][turtl_core::sync] sync::start() -- incoming shut down (run 1)
2020-11-23T12:01:26 - [INFO][turtl_core::sync] sync::start() -- outgoing shut down (run 1)
2020-11-23T12:01:26 - [INFO][turtl_core::sync] sync::start() -- files:outgoing shut down (run 1)
2020-11-23T12:01:26 - [INFO][turtl_core::sync] sync::start() -- files:incoming shut down (run 1)
what i noticed is that it generally happens when i close the window via X button which is at the top-right of the screen (it's because "freeform mode" is open in developer options)
so i always navigate back instead of closing. so it's doing ok for now. yet i still have this issue time to time.
I believe this was cause by a DB issue that is now resolved. Can everyone confirm this is working now? Thank you.
I believe this was cause by a DB issue that is now resolved. Can everyone confirm this is working now? Thank you.
I'm still having but -as i said- only when I close the app via X icon.
I believe this was cause by a DB issue that is now resolved. Can everyone confirm this is working now? Thank you.
@orthecreedence, I haven't received this problem since yesterday.
@frknltrk, I suggest close this issue (reopen if it happens again).
I believe this was cause by a DB issue that is now resolved. Can everyone confirm this is working now? Thank you.
@orthecreedence, I haven't received this problem since yesterday.
@frknltrk, I suggest close this issue (reopen if it happens again).
alright, thank you everyone.