Hi Rena, Glad that helped you too. In the test area of the service you will not be able to store it to a local storage variable yet, but you can do that in one of your service calls, probably one of the first things you do in your app is to let the user log in and then during this login service call...

Hi Rena, Not sure if this would help, but I too spent most of my weekend trying to figure out what is different with my call to DreamFactory when I do it through my RESTClient on Firefox and then when I do it through Appery.io. What made the difference for me was that in the live api documentation y...

Hi Mark,

That works great - thank you for the assistance, much appreciated.

Hi Evgene, This is what I get in RESTClient (which is what I expect): https://d2r1vs3d9006ap.cloudfront.net/s3_images/1096655/Capture1_inline.JPG?1410252369 This is my setup on the service: https://d2r1vs3d9006ap.cloudfront.net/s3_images/1096656/Capture2_inline.JPG?1410252500 And this is what I get ...

Hi, I found two similar questions on the forum, but none of them actually seemed to have an answer posted and I am unsure of how they managed to fix it. The problem is, I am using DreamFactory and created a new service in my app to make a call to my DreamFactory REST API via the AppBuilder's Request...

Hi,

Yes, that seems to have resolved the problem.

Thanks for the quick response, much appreciated.

Hi, I'm still pretty new to Appery.io, so please excuse me if I have not read all the documentation that might pertain to this specific issue. I started developing my app by calling the normal (generated) service requests created from importing them from the database services, but then I decided tha...

I had the same issue before. After I deleted a service that I have already referenced in one of my pages and then attempted to open a page with this 'deleted' service link it would just not open the page anymore. I ended up deleting the page and creating it again. I'm sure there is some sort of work...

Hi, I'm going to take a wild stab at this, but I had a similar problem yesterday. Do you have an event on the 'error' condition of your request to the login service? If not, try adding an event there and alert the error message. In my case it also worked during initial testing on the app test and on...