mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 04:46:56 +00:00
[GH-ISSUE #4904] [Bug] login with github account,missing field icon at line 1 column 540 #2176
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#2176
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @qeuyee on GitHub (Mar 15, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4904
Originally assigned to: @speed2exe on GitHub.
Bug Description
How to Reproduce
third-party sign-in
Expected Behavior
missing field
iconat line 1 column 540Operating System
win11
AppFlowy Version(s)
0.5.2
Screenshots
No response
Additional Context
No response
@speed2exe commented on GitHub (Mar 15, 2024):
Hi, @qeuyee
I am unable to reproduce this on Win11.
I want to gather more information on this.
@qeuyee commented on GitHub (Mar 15, 2024):
I have set up a private Appflowy Cloud and use my GitHub account to log in. However, I have encountered the following main issues:
1.Before the AppFlowy version 0.5.1, it could be used normally, but there were issues with data synchronization. The data could not be synchronized to the mobile app or to another computer where I logged in with the same account on AppFlowy.
2.After updating to version 0.5.1, it automatically logged me out during use. When trying to log in again with my GitHub account, an error occurred with the following error message: "error message: code: UserUnauthorized msg: sign in with oauth error -10003".
3.After updating to version 0.5.2, I still could not log in with my GitHub account. The error message was: "missing field icon at line 1 column 540".
@speed2exe commented on GitHub (Mar 15, 2024):
@qeuyee Are you self-hosting AppFlowy Cloud?
@qeuyee commented on GitHub (Mar 15, 2024):
yes
@speed2exe commented on GitHub (Mar 15, 2024):
@qeuyee You might need to update the appflowy-cloud images. you can do
docker compose pull, thendocker compose up -dto use the new images.@qeuyee commented on GitHub (Mar 15, 2024):
thanks
Thanks,After the update, are the data that I previously synchronized still there?
@speed2exe commented on GitHub (Mar 15, 2024):
@qeuyee yes it will still be there
@qeuyee commented on GitHub (Mar 15, 2024):
The problem has been resolved.
@qeuyee commented on GitHub (Mar 15, 2024):
Does the AppFlowy Cloud need to be synchronously updated every time the AppFlowy version is updated?
@speed2exe commented on GitHub (Mar 15, 2024):
@qeuyee
This does not happen for every update, this happened because the schema changed in the desktop app but the server still retains the old schema.
As much as possible, we will also keep them backward compatible.
Thanks for raising this issue, we will try to maintain backward compatibility with server.
@DevaanshPathak commented on GitHub (Mar 22, 2024):
@annieappflowy please close this issue as it has been resolved