Suddenly, things that worked before are not working anymore. For everything that I’m trying to save to Backendless I get the following error:
FAULT = ‘1000’ [Entity with the specified ID cannot be found: Id - missing id] <Entity with the specified ID cannot be found: Id - missing id>
The information is retrieved from the database successfully. I get an error only when trying to write to DB.
I checked the app id and I regenerated the secret key, but I still get the error.
Can someone tell me what’s going on? Thanks
Your not alone this is affecting a ton of people according to all the other error 1000 posts here
Do you save a new object or update an existing one?
I’m saving a new object.
I just tried saving an object from a sample Java program, it worked. What does the class look like for the object you cannot save?
class Post: NSObject {
var ownerId: String?
var objectId: String?
var created: NSDate?
var updated: NSDate?
var replies: Int = 0
var text: String?
var score: Int = 0
var location: GeoPoint?
var imageURL: String?
var image: UIImage?
var dummyPost: Bool = false
}
Like I said in the post, it doesn’t really matter. I get the error for all objects. They were working before, I haven’t changed any code since they were working.
Please update the following two libraries from github (click on “View Raw” to download) and it will work:
https://github.com/Backendless/ios-SDK/blob/master/SDK/lib/backendless/backendless.a
https://github.com/Backendless/ios-SDK/blob/master/SDK/lib/CommLibiOS/CommLibiOS.a
I updated the pods. I don’t know if it’s going to work now (probably it will) because I’m getting errors in my code after the update.
A few questions though.
In case my app would have been live, after this change in your libraries, none of the people using the app would have been able to save objects to the DB? And for them to do so again, they would have had to update the app?
Moreover, you also changed the syntax of some objects and functions. Are the changes documented somewhere?
And did we get notified in any way of this change and I missed it?
The change in the update behavior is a regression which will be fixed asap. Normally you would need to do the update.
What syntax changes do you observe?
func application(application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: NSData) {
let deviceTokenStr = backendless.messagingService.deviceTokenAsString(deviceToken)
let _ = backendless.messagingService.registerDeviceToken(deviceTokenStr)
let _ = backendless.messagingService.registerDevice(["default"])
}
I now get an error on backendless.messagingService.registerDeviceToken(deviceTokenStr). It expects an NSData object instead of String!
let publishOptions = PublishOptions()
publishOptions.headers = data
Cannot assign value of type ‘[String : String]’ to type ‘NSMutableDictionary!’
For (1) it would mean you can strip out some code from your which used to convert String to NSData (the underlying method accepts NSData
For (2) I would need to defer to our iOS devs. The code from github is a pre-release before it goes on our website), there might be some things which are not final.
Is there a fix like this for Android and .NET Libraries? It appears to be effecting all platforms.
It does work with the latest released SDK for Android from our website. The latest build is in github:
So right now I’m left with a non working app…
It’s pretty bad what just happened. Not only the syntax change but necessity of the update too.
Is your app in development or in the app store?
What about .Net? I dont see any updates on github so i assume you guys are working on it. It definitely makes me really nervous that my app (which is currently in development) has been offline all day now…
It’s in development. However, I can’t help to wonder if things like this will happen once it’ll be in the app store.
We’re talking about removing a few lines from your code (thus making it cleaner).
If you want a guaranteed SLA for service and support, you’re welcome to contact sales and arrange a support plan.
Got it
Hi Matthew,
It is being worked on.
Regards,
Mark