Thanks Mark, yes I’ll use the File API then and I can find the path on my phone no problem. So then do I use the copy file API? I’ve tried this just using a basic image file already saved in my web folder on backendless and get this error:
{
“code”: 6007,
“message”: “The specified resource was not found”,
“errorData”: {}
}
You can use the “Copy File/Directory” when you need to copy a file that already exists in the Backendless file storage to another directory.
Please use the following doc to see the semantics for the “from” and “to” arguments: https://backendless.com/docs/rest/file_file_copy.html
Ok I found the multi-part/form data piece that should form the request body.
Trying to figure out how to send an image in multi-part/form data now… any suggestions welcome!
After selection a mandatory header (multi-part/ form) you need to select in the request body the form-data type and as a value the full path to this file on your device.
As example my curl looks like this:
POST https://api.backendless.com/<application-id><REST-api-key>/files/Exapmle.png \
--header 'Content-Type: multipart/form-data' \
--form '=@"/path/to/file"'
I think that question would be better addressed to AppGyver’s support. We can assist with backendless api, our own UI Builder, but when it comes to third party tools, we cannot provide support for them.
@Joel_Maclean - did you have any luck with this? I am getting nowhere at the moment! I am going thru the appgyver documentation and forums and no such luck
Yea no progress @sim_sim , I posted in Appgyver forums to ask for paid help and can’t seem to get anything going. A few guys replied but no one responds outside of the forums.
@mark-piller basically yes, they warn the users that its not supported and that they rely on community support. Trouble is the ‘community’ is very small
@mark-piller I do think it complements your product quite well. I did try to use your front end but the functionality has a ways to go to catchup to Appgyver, also Appgyver has a build component that allows us to build packages to publish in the app stores and web app servers.
Here is a screen shot of where you configure an API call, as you can see there’s an option to set a header, but not sure where to go with the --form piece @Marina.Kan mentions. Happy to entertain any suggestions here .
Haha touche @mark-piller. And agree.
The native app (ability to run local storage), and charting (google charts plugin) I’d say are the main differentiators. I essentially built an mvp on backendless’ front/back end and had to switch to appgyver for a front end when I discovered the charting options. I’d be happy to beta any features you guys are working to help refine/grow your product.
In the documentation for the API it shows the format using curl, but is there a way to reflect how that format translates to a web call? Like where does the --form piece go? can it go in the URL as a parameter?
.
