Sync issues on panels

#1

Hi,

I am having sync issues between my panels app on the iPhone and the iPad

In the app, I have logged into the same apple id on both devices.

I have imported the same files into both devices.

But when I read on one device, it does not pick up the progress on the other app.

Please advise

#2

Continuing the discussion about the reading progress syncing issue from Can I store my comics in icloud? - #9 by victor

@Ivan_Belousov @rincewind could you folks try changing your profile image in Panels? Does it work? I’m trying to understand if it’s the issue is only with the reading progress service, or communicating with the backend at all.

Can I store my comics in icloud?
#3

Hi there, I have just tried changing my profile pic and name in Panels. I did it on my iPhone then I checked on my iPad, on my iPad none of the changes are applied. Also, I noticed that if I log out and log back in my name gets reset to default.

#4

767BE6A9-6F5C-4CD9-815B-9F824C024F89_1_201_a
767BE6A9-6F5C-4CD9-815B-9F824C024F89_1_201_a1920×1130 234 KB

#5

Hi @dani , thank you for the response

So between posting and before seeing your response, I changed the login method from apple to Google, in the hopes that it would work. It was still the same.

After reading your response just now, I went into the iPad app, and changed the profile picture. The change in profile picture doesn’t reflect on the iphone app.

#6

Thanks for all the info!!

Are you folks using iCloud’s Private Relay?

IMG_C571FE930582-1
IMG_C571FE930582-11179×2556 105 KB

I found this issue in Firebase’s SDK repo where it looks like some iOS versions are blocking some requests.

@Ivan_Belousov, using the information in your screenshots, I was able to find your user accound and see the changes stored. Currently, the username stored on our backend is “Ivan.” So, it looks like your iPad is not picking up. Also, I saw you have 20 reading sessions synced, so the information is being stored on our backend.

Let me know if you use the Private Relay. The problem might be that iOS is blocking communication with our server.

In the meantime, I just upgraded Firebase SDK to its latest version, and I’m going to make the user ID visible on the profile screen so it’s easier to see if both devices are actually logged in with the same account. These changes will be in the next Panels release. Probably 3.4.10.

#7

Thank you for the response! Yes, I’m using Apple Private Relay. I’ve been mostly reading on my iPad, and my reading progress is a little ahead compared to my iPhone. For example, I have completed ”Deadpool Kills The Marvel Universe“ on my iPad, but on my phone, it only shows 20–30% completion. But hey, I’m looking forward to the changes in the next update.

#8

Just to be clear, I don’t think my changes will resolve this. If the Private Relay is the issue, either Google or Apple will have to figure this out and it’s most likely affecting other apps too.

Could you try disabling the Private Relay momentarily on both devices, and try updating your reading progress to see if sync works both ways?

#9

I just checked both of my devices and icloud private relay is turned off for both of them

image
image1290×2796 210 KB

#10

Thanks! It must be something else, then. I’ll keep digging.

#11

Hello @dani , just wanted to check if you had any luck with the sync issues. Thanks

#12

We haven’t found anything. A couple of days ago, we released a new beta. Could you install it? Discord

In this new build, the profile screen shows your userID. Can you install the beta on both devices and check the userID is the same?

#13

Today, we released the beta version in the AppStore. You can install the latest version on the AppStore and find your userID in your profile section.

Give it a try and let me know if both of your devices are logged in with he same account id.

#14

Hi @dani , thank you for pushing the update. I was looking into installing the beta but the update was pushed to the app store before I could do that.

I can see that both of my devices have the same userid.

Would you like me to share it? Can I send it over in a direct message?

I can see that both the devices have a different support ID however. Not sure if that’s relevant.

Thanks

#15

Thanks! yes please, send me a screenshot over DM. :+1:
I’ll try to find logs on our server.

I can see that both the devices have a different support ID however. Not sure if that’s relevant.

Support identifiers should be identical if both devices use the same Apple ID. But in some scenarios, they can be different. If iCloud Keychain is not enabled, for instance.

But that doesn’t affect the content synchronization at all. As long as the user ID is the same, both devices use the same account.

I’ll keep investigating. It might take me some time to figure this out, because we’ve only received your reports, and we can’t reproduce it on our end. We must be missing something :thinking:
In the next beta/release builds, I’ll add more remote logs into the app to gather more data.

#16

I have sent you the screenshots over DM. I think I may have started multiple threads in the messages but I’ve sent both the screenshots. Thank you

#17

Thank you! :raised_hands:

Let’s see if I can gather any information with your IDs and figure this out.

Thanks for your patience :pray:

#18

Just dropping in to say I’m having reading progress issues with Panel

#19

Hey folks! We just released a new beta build, which includes remote logs to gather more information about the syncing issue.

It would be great if you could install it on your devices and use it normally.

#20

Hi folks @rincewind @Curtis_Barber @Ivan_Belousov

Is there any chance any of you have the data/time manually set on your device, instead of automatically synced with the internet/GSM provider?

I got some new logs with Denied Access errors from the server. That can only occur if the app tries to update the reading sessions of the wrong user (very unlikely because the userId is automatically resolved by Firebase’s SDK), of if the reading session sent to the server is older than the one stored on the database.

Having the date/time set incorrectly on the device could cause this issue.