I will wait to othres to response to this issue, maybe the cloud backup is one of the root cause of this issue
everyone
can someone help me to this issue
I am still encountering this issue
This shouldn't happen because of a backup. @Mosh Ontong do you get any errors in your browser? can you check using your devtools?
Also, are you able to access this doument using the API?
it actually successfully fetch the document based on the network tab and no error occurs but in my dashboard does not show the documents data
Can you share the document structure? It sounds like a UI problem if this is the case.
In I just check the console in dev tab right now this is the error
but fetching the payload in server no error occur
@Torsten Dittmann could you or someone from the console team take a look at this?
The backups only cause problems with schema changes like creating an attribute or creating a collection
That's the problem. Malformed permissions
what do you mean malformed permission? if it is how to fix then?
It should be an array. You can try to update it
you are right I just created a dummy document, I create this dummy through console and yeah it sucessfully loaded. I think we should have feedback on console ui here if this issue occured, I cant delete this document because of this issue
This is my code to create a document
final doc = await databases.createDocument(
databaseId: super.bookingTimelineCredential.databaseId,
collectionId: super.bookingTimelineCredential.collectionId,
documentId: ID.unique(),
data: bookingTimeline.toJson(),
permissions: [
Permission.read(Role.users()),
Permission.update(
Role.user(
bookingTimeline.bookingRef.clientProfile.id,
),
),
Permission.update(
Role.user(
bookingTimeline.bookingRef.service.ownerId,
),
),
Permission.delete(
Role.user(
bookingTimeline.bookingRef.clientProfile.id,
),
),
Permission.delete(
Role.user(
bookingTimeline.bookingRef.service.ownerId,
),
),
],
);
Every I create a document then this malformed will always occur? But when I create document through console the malformed permission will not occur
Ah yes that makes a lot of sense π
The thing is we should never let the permissions get malformed so it's a backend problem, not a console problem
Maybe the client id and the owner id were the same?
yes it is
For now, you'll need to make sure you're passing unique values. On our end, we'll need to handle this better
ok this will be noted thanks steven
[SOLVED] Document cannot load
btw, looks like this fix will be in appwrite 1.4.0: https://github.com/appwrite/appwrite/issues/5661
Recommended threads
- Cloud function deployment failures
When I run appwrite push functions, select the function I want to deploy, confirm with a YES, is starts deploying but goes into error. I need to repeat the ste...
- 1:1 relationship doesnβt sync after re-a...
Hi, Iβm trying to use a two-way one-to-one relationship. It works fine when I create a record with the relationship set, and it also works when I unset it. But ...
- Upsert with setting permissions
Hi there, I am using self-hosted appwrite v1.7.4 and trying to use the bulk update stuff that was released with 1.7.x. Unfortunally I found that there is an ser...