search

astubenbord / paperless-mobile

An (almost) fully fledged mobile paperless client.
GNU General Public License v3.0
720 stars 36 forks source link

Compatibility with older versions #17

Open Totil-a opened 2 years ago

Totil-a commented 2 years ago

I can see all documents and their metadata correctly.

As soon as I change something, be it correspondent or tag and save it, I get: 'Document successfully updated' followed by 'Could not update document. Please try again' message.

What could be the reason?

I am 1.0.3+1, installed from Google play store.

astubenbord commented 2 years ago

Hi, this is probably related to the bad error handling design which I'm currently improving. This should hopefully fix this. I'll notify you once I've updated the code and I'll add a new release, since some useful features have been added since 1.0.3.

astubenbord commented 2 years ago

@Totil-a could you try out the new release (https://github.com/astubenbord/paperless-mobile/releases/tag/v1.0.4-beta) and check if the issue still persists? A new release in the Google Play Store is also currently being reviewed.

Cheers

Totil-a commented 2 years ago

@astubenbord just did. 'Could not update document. Please try again' appears immediately when I press the save button. I removed a tag and wanted to save the change.

astubenbord commented 2 years ago

Which device are you on (Model and Android Version)? And which paperless Version do you have installed on your Server? I cannot reporduce the issue on my own device unfortunately.

Totil-a commented 2 years ago

Pixel4a and android 13

Paperless ngx server version: 1.8.0 (let me try updating to latest and report back)

Totil-a commented 2 years ago

Updating to 1.9.2 resolved the issue. Documents changes now save correctly.

astubenbord commented 2 years ago

Great, thanks for the update. But I think for downwards compatibility, it would still be good if I could resolve this. I think it could have to do with the API versioning, as version 2 did some changes to the tags model. I'll have to look into why this happens. I'll reopen the issue until it's fixed for older versions as well. Cheers!