Writing right needed for the ios app to works

[ewok2]

Hello

NC : 29.0.6
Cookbook : 0.11.1

Not sure if it is a bug or wanted point...

I have a cookbook on my account.
I want to share it to other NC users.
I have share the directory reciepe to the other user in read only. (I don't want him to be able to modify my reciepe)
The first time you open cookbook in the other user NC web, it say the directory choosen should be write enable to allow other user to add reciepe. But it works for other user to read the reciepe with the NC App.
But when the other user install the IOS App, the app succeed to connect to cookbook but can't show any reciepe.
=> as soon as you add writting right to the user the ios app see all the reciepe.

Idealy if cookbook ios app coumld works without wirting right?

[VincentMeilinger]

Hey @ewok2,
Thank you for the feedback!
This is interesting to hear. The app should still be able to access your recipes if the user has read access only to the recipe folder. Unfortunately, I likely won't be able to help you here, since API access control is performed by your Nextcloud server, not the Cookbook app. You should probably file an issue on the Nextcloud Cookbook Github page for this.

[ewok2]

Hello Vincent
I initially thought that it was indeed a server issue. I let a issue @christianlupus.
nextcloud/cookbook#2488

And i say it may be an issue on the ios app side.

I known the interface is alway complicate between client and server ;-)
I personnaly I have no idea which side is the error....

But I am available to help in case you or christianlupus need more information if you can not reproduce the error on your side.
I have a NC on a VM and can perform test even "dangerous" as I can restore easily :-)

[christianlupus]

Hello. The point here is that the web frontend is generally able to view the recipe according to the user's claims. That would mean that the problem is in the API between backend and app/frontend. I am on the route ATM but I can try to reproduce the issue locally and see if I can dump the network traffic. Then you can check if the iOS app is capable of handling this input. Was this something we can do? Or do you have a better idea?

[VincentMeilinger]

Hi @christianlupus and @ewok2,
Apologies for the (very) delayed response! I’ve decided to rework the entire API since there seem to be multiple issues with it. I plan to do this in the coming months.
If the issue is still there after that, I’d really appreciate your help to figure it out. Thanks for your patience!