-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not put (-30786) (10199) #72
Comments
@debmalyakar Could you please adjust the issue text and ensure you provide the information the issue template asks for? That would be helpful to give you a better answer. Thanks. |
I have adjusted the issue text according to the template. Kindly let me know if you need added information. |
Thanks for the additional info. I believe a similar issue was reported on another platform. It's likely related to the unique constraint; so maybe we can track it down starting with that assumption. Can you tell somehow if it occurs in certain conditions only, e.g. if the unique constraint is violated? |
I removed the unique constraint but the error still occurs after removing. |
Thanks, if it's possible that you share the Xcode project (or a reduced sample project), we would be glad to look into it. PS.: Does this only occur on the said iPhone, or also using the simulator? |
I'm trying to create a reduced sample project that will have the same issue. I'll surely share if i can create similar issue there. I tested on the simulator (iPhone 12 mini , iOS 15.5). It is working fine on simulator. The problem only occurs on device. |
I have made another observation. var requestorVisible: Bool The insertion process works fine. Is there any sort of limitations on the number of properties in an Entity class that i may have missed from the documentation ? |
In theory no; we have test for these cases and know of successful apps that have lots of properties. However, you may be hitting some problematic scenario... |
Can you please share an email id where i can share the Xcode project? |
markus |
I have sent you a demo project replicating the error on the above email. Please let me know if you have received the code sample. Kindly go through the code and let me know if we are missing anything that might cause the problem. |
Thanks, I received it. |
Kindly go through the code and let me know if we are missing anything that might cause the problem. |
If possible kindly let me know of any workarounds to solve this issue... |
Status update: after removing the unique constraint, the project you sent me was able to put all objects. PS.: Adding a |
An actual fix was completed internally. We'll likely release a 1.8.1 patch version soon. |
Fixed in 1.8.1, which was released Jan 30th. If possible, it'd be great to have your feedback on this. |
Describe the bug
While trying to insert around 200 records the following error is received.
Basic info (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It is expected that the data should be inserted in the database on "put" statement.
Code
If applicable, add code to help explain your problem.
This is the method that have been used to insert -
try assignmentBox?.put(assignments)
assignments is an array.
Logs, stack traces
Additional context
Add any other context about the problem here.
Nothing special is done. Server is called and the response is being tried to insert into database.
Transactions is not used.
Not as of yet.
Kindly let me know the probable cases where this error may appear.
The text was updated successfully, but these errors were encountered: