Hi,
I am trying to add server side code for my iOS app. I’v succeeded adding users service event handler and custom event handler, however, there’s problem adding handler for data table.
I get below error when running data table server code.
argument type mismatchjava.lang.IllegalArgumentException: argument type mismatch
To find if it’s mapping issue, I created very simple temporary Test table which has only 1 custom field of type STRING. There no problem with below code if I remove server code “afterCreate Test table”.
I’ve attached server code files except for bootstrap.java.
bootstrap.java contains Backendless.Persistence.mapTableToClass( “Test”, Test.class );
Test* entity = [[Test alloc] init];
entity.str = @“sdfs”;
[[backendless.persistenceService of:[Test class]] save:entity response:^(Test* newEntity)
I have attached server code files.
How do I actually implement above identity check code. Unlike custom event, I can not return anything, then how can client program know that it failed due to same identity. The below is what I have, if you could provide example, that would be great.
public void beforeCreate( RunnerContext context, ChatGroup chatgroup) throws Exception
BackendlessCollection<ChatGroup> result = Backendless.Data.of( ChatGroup.class ).find(dataQuery);
if(result.getData().size()==0) //create new entity only the same identity does not exist
super.beforeCreate(context, chatgroup);
}
I have no idea except for not calling super.beforeCreate to prevent new creation.
Do I need to call parents function? For user service handler, not calling super.afterLogin still works.
Business logic execution time for Cloud Enterprise Plan is 120 seconds. If I have “beforeCreate” function implemented on the server, does it mean that actual creation time will be less than 120 sec even if the call is synchronous call? I wouldn’t receive response for 120 seconds?
Direct invocation of custom server-side code takes 120 sec as well?
Thanks for reply.
I tested with iOS device, using REST API instead of iOS SDK, and it works!
I will change my codes(ones that invokes server side code) to use REST.
If I find need for using iOS SDK or any problem occurs I will get back to you.
With help from Slava, I’ve managed to send push notification from iOS device.
On some cases I send notification from server code.
I implemented server code to send push notification after create data table entity.
Running the code, I get the following message.
“User has no permission to publish message”
I think it’s another ACL issue, just like the file download problem from my previous question.
I’ve attached source code and capture of channel permission settings.
I enabled role permission of Publish HTTP Post for NotAuthenticatedUser.
Message is delivered without error, but push isn’t sent, the below is message status printed from server code.
Just to clarify:
In this app push notifications sending and receiving works properly if publish them via ios sdk?
You have problems just with server code?
Hi Kate
In this app push notifications sending and receiving works properly if publish them via ios sdk?
Push notification sent through backendless iOS SDK can be received by the receiver.
You have problems just with server code?
Yes problem only with server code.
Push notification sent through server code using java sdk (backendless.jar) CAN NOT be received by the receiver.
Just to make sure you that you know, it has ACL problem as I wrote previously.
“User has no permission to publish message”
According to the ACL problem:
you try to publish message from server code as NotAuthenticated user.
Thats why this error message is correct.
You can add some admin user, GRANT “publish” permission for him and
login admin user in server code before publishing.
I will check problem with receiving push notifications. It will take some time.
I have simple question to ask.
Setting server code event handler to async from console, does that mean your web server will respond immediately to a http request, and server code will be executed anytime after http request has been received by the server?
I’m almost done migrating Backendless from previous baas I used.
There’s one problem, and regarding this problem, I sent email to Mark yesterday, but I thought that he might be busy or may not have received my mail so I am writing in.
I totally understand that fixing “sending push by server API” problem will take some time. I just want to know how much time it will take - if it takes weeks to fix, I will use iOS client SDK for sending push.
The thing is that I found some problem sending push with backendless iOS SDK. I don’t think it’s a iOS SDK problem, but rather backendless push server issue and iOS7/8 support issue.
sending push with data more than 256 bytes
From iOS 8, push message size is 2 kilobytes max, but as I tested sending push using iOS 8 devices, it fails with error “length greater than 256”. I guess your server does not support iOS 8. I can limit the length of text that’s no problem.
The real problem comes after getting size limit error - whenever I try to send from a device A to device B, it fails with error “Socket Closed” for many times. I tried sending from B to A, but it fails with the same error. I wasn’t able to send push for while, something like 15 min. I actually had some “socket error” before, back then I sent message from console, not lengthy ones though.
As push notification is critical feature, is it possible to stablize push server? (exception handling, socket reconnect, etc)
Receiving data in background mode
Unlike android device, there’s no way to receive push notification when the app is in background mode prior to iOS 7.
For iOS 7+, apple introduced silent push notification, which made possible for app to receive push notification when the app is in background mode.
If you take a look at below Apple document, it’s “content-available” APNS field that needs to be added when sending push to apple server.
Can you add this feature?
Thank you for this message too!
You say
I totally understand that fixing “sending push by server API” problem will take some time… >>
you mean sending push messages from server code? Yes?
Currently I cannot say how much time it will take.
I will notify you tomorrow, ok?
sending push with data more than 256 bytes >> currently we are working on these problems.
Receiving data in background mode >> yes, we will add this feature in a few next days.
It will take several days to implement new feature and to check bug fixes.
I am sorry if I bugged you and your team too much.
It’s just that I was kind of nervous about the fact that I spent almost 3 weeks, migrating from different BaaS, may not release my app soon due to push notification issue. Apple reserves app name for only 6 months and I only have a week to finish before losing my app name, then I would have to redesign icons, screenshot, website, etc. I hope you understand.
Using the service for several weeks, I truly think that Backendless is the best out of all the BaaS’ I used so far. It would’ve been a lot better if I had known about Backendless earlier.
I really appreciate your support.
In this case your push notification will be received by all devices, registered to the channel you specified as the first argument in your Backendless.Messaging.publish( … ) method call.
You can also send push notification only to Apple devices:
Yes, in iOS SDK the DeliveryOptions.pushBroadcast = IOS by default, so iOS devices can receive the push notification without any setting for it.
Now about the features “Push notifications don’t maintain the “content-available” key of notification payload” & “Push notifications don’t maintain the “alert” with size more then 256 symbols (2K is allowed)”: they were fixed, QA yet will check them, so they will be deployed on the production in the beginning next week.